FiveTech Software tech support forums

... con unos caracteres especiales de separador de campos que me estaban modificado la cadena del IP y por eso no funcionaba.. #define SE chr(28) CallDll32 ( 'MandaPaqueteFiscal' , 'WINFIS32.DLL' , nHandler , CHR(163) ) CallDll32 ( 'UltimaRespuesta' , 'WINFIS32.DLL' , nHandler , @cRta ) cRta:= ...

... "user32.dll" ) == "C", "user32.dll", Str( "user32.dll" ) ) ) ; end ; return uResult Y la otra opción, CallDll32, ya directamente es una función de FW. Alguna sugerencia... o cual foro Harbour donde poner mi petición??? Gracias.

Esto es con la funcion CALLDLL32 de Fivewin, no se si te servira. nHandler := CallDll32( "Funcion" , "ARCHIVO.DLL" , nParam1 , nParam2 )IF nHandler >= 0     CallDll32( "OtraFuncion" ...

... Function AbrirPuerto(nPort) *-------------------------------------------------------------* local lResp:=.T. nHandler := CallDll32( "OpenComFiscal" , "WINFIS32.DLL" , nPort , 1 ) If nHandler >= 0 msgalert("Puerto de impresora OK ") nError ...

Hi Antonio, At this time i have just found this in BCC582\INCLUDE\WINABLE.H about GetWindowModuleFileName(), nothing about CallDll32(). Please, where are located GetModuleFileNameExA() and CallDll32() ? #if (WINVER < 0x0500) // these structures and functions            // ...

Hi All, I return on the FW forums after long time of silence. This week i begin with FWH 13.7 and i have found 2 unresolved externals, for CallDll32() and GetModuleFileNameExA() listed below : -------------- Turbo Incremental Link 5.69 Copyright (c) 1997-2005 Borland Error: Unresolved external ...

Antonio, I updated the libs but I'm still getting a CallDll.c / CallDll32 MessageBox. http://farmacia.com.br/CallDll32.png I made a small self contained sample TESTE.PRG: #INCLUDE "fivewin.ch"FUNCTION MAIN()   Local hHandle  ...

... pN ) or IfNil( { a1. ..., aN } ) --> first non-nil value. * Enhancement: Improved sample xbrwdisk.prg. * Enhancement: functions CallDll() and CallDll32() have been renamed as FWCallDll() and FWCallDll32() to avoid symbols clash with Harbour. Please recompile all your PRGs and check if you ...

... Barpaint() BeginPaint() Bin2d() Bindtoport() Bitblt() BringWindowtotop() Browse() Btndisable() BtnPaint() BuildCommDCB() C2Hex() CallDll() Calldll32() CallWindowProc() cArgV() cChr2Data() cCtrl2Chr() cDlg2Chr() cFileDisc() cFileExt() cFileMask() cFileName() cFileNoExt() cFileNoPath() cFilePath() ...

... METHOD PEOPEN_() LOCAL cFarProc LOCAL cFunc := "PEOpenEngine" IF ::l32 cFarProc := GetProc32( ::hDLL, cFunc, .T., LONG ) ::lError := ( CallDll32( cFarProc ) == FALSE ) ELSE cFarProc := GetProcAddress( ::hDLL, cFunc, .T., _INT ) ::lError := ( CallDll( cFarProc ) == FALSE ) ENDIF IF ::lError ...

... */ METHOD PEOPEN_() LOCAL cFarProc LOCAL cFunc := "PEOpenEngine" IF ::l32 cFarProc := GetProc32( ::hDLL, cFunc, .T., LONG ) ::lError := ( CallDll32( cFarProc ) == FALSE ) ELSE cFarProc := GetProcAddress( ::hDLL, cFunc, .T., _INT ) ::lError := ( CallDll( cFarProc ) == FALSE ) ENDIF IF ::lError ...

... 99.71 - gpf's are occuring under various circumstances. Using xharour 99.5 - no problem. question - what's the reason I would choose calldd or calldll32 for dynamically calling an external dll. Aren't all dll's 32-bits these days? My mystery is, if I use getprocaddress(), loadlibrary(), freelibrary(), ...

... that tMutex.prg does have the following at the bottom of the tMutex.prg (see end of mail) So that would mean the fwh calldll.c function 'CLIPPER CALLDLL32( PARAMS )' is being called instead of the 'Function CallDLL32' below (in tMutex). This should only happen if calldll.c (in FiveHcm.lib) is ...

... a Fwh and xHb aplication using latest Sept/Oct2006 Fw28/xHb This app call the tMutex.prg class Create method below. The tMutex create method calls CallDLL32(.....). In my application when CallDLL32 is called, i get a pop up msgalert "CallDll32", with a title of "calldll.c". I have tracked this ...