FiveTech Software tech support forums

... : I understand this is all you will need to build and test. Again, I believe the problem is with my wrapper functions or the structure declarations. The GPF happens when executing TOCRDoJob2(). Here is my new source: request hb_gt_win   //needed for console mode app.#define TOCRJOBTYPE_TIFFFILE ...

... to be available in WinINet.dll. The function I need is FtpSetCurrentDirectory(). My question is how do you know how to write the "DLL32" declarations. DLL32 Function FtpSetCurrentlyDirectory( hFtp AS LONG, cDirName AS LPSTR ) AS BOOL PASCAL FROM " FtpSetCurrentDirecotry " LIB ...

... to be available in WinINet.dll. The function I need is FtpSetCurrentDirectory(). My question is how do you know how to write the "DLL32" declarations. DLL32 Function FtpSetCurrentlyDirectory( hFtp AS LONG, cDirName AS LPSTR ) AS BOOL PASCAL FROM " FtpSetCurrentDirecotry " LIB ...

... at the top of the file, then I would only get warnings for undeclared locals. Once I got all those declared, then I could remove the MEMVAR declarations and get warnings for all the publics. What's your plan? PUBLIC => STATIC and PRIVATE => LOCAL? SublimeText and xEdit has wonderfull ...

... strings of letters with no meaning. I presume this was done since when I first worked with this code many years ago, there were no variable declarations, so everything was private. Thus every variable name had to be unique across the entire program. Maybe I actually could do both. First ...

... the code. However it's hard to maintain 100% concentration on such a massive project. Ultimately I'll be able to eliminate 100% of any automatic declarations, and have everything super fine tuned ... but it is a massive project. It's one thing to convert the shell of a program, but yet another ...

... from my computer when I last responded. Now that I have been able to lookup the /a, I remember why I don't use it. I don't want automatic memvar declarations since I am trying to document all vars used in each function. This is mainly so I can look for locals and privates that may be overriding ...

I never use PUBLICs, but today I am working on someone else's code and there are PUBLIC declarations. I kept getting "ambiguous reference" warnings for the PUBLICs. I finally figured out that it was only for those PUBLICs that are also initialized in the PUBLIC ...

Nageswaragunupudi,
Delete dll declarations , run OK!
TKS!
Shuming Wang

I do not thing bas.prg and FIGETFILETYPE() function are not from FWH. If you just rely on DLL declarations inside Image.prg without any modifications, there should be no problem. For example, this small sample works well. function test()   local cSrc ...

... .t., .t. ) } )USE DESTINATION.DBF NEW ALIAS DSTDST->( FW_ArrayToDBF( aData ) )  function headers, variable declarations can be added. This logic preserves CRLFs and commas with in double quoted strings.

... <---- error The C++ language allows that, but not the C language. So take that line under the above variables declarations: LONG lStatus; DWORD dwLastError; WINTRUST_FILE_INFO FileData; GUID WVTPolicyGUID = WINTRUST_ACTION_GENERIC_VERIFY_V2; <---- error ... ...

... at 'STATIC'" classes\dialog.prg(526) Error E0030 Syntax error "syntax error at 'STATIC'" 3 errors These are due to the following declarations. As it is a syntax error I'm assuming it is another improperly referenced .ch file. But, as I am compiling this with msvc, I am not sure ...

Nothing important but there are still two METHOD Refresh declarations in tmsgitem.prg.

EMG

... much of the same information you already know or currently use .. Also, I have found that you should try to use Locals for your oRs variable declarations and pass them as parameters to your various functions. If you do use Statics .. you may run into situations where you get variable creep ...