FiveTech Software tech support forums

... you explain? Here in Brazil, there are many reports that when compressed with UPX.exe, most ANTI VIRUS do not accept the .EXE, as they say it is a suspicious file. This is why I stopped using UPX.exe Aquí en Brasil, hay muchos informes de que cuando se comprime con UPX.exe, la mayoría de ANTI VIRUS ...

... UNICODE#include "fwh.h" Question : why "#undef UNICODE" :?: --- now i get Warning Warning W8075 .\\HB_FUNC.PRG 702: Suspicious pointer conversion in function HB_FUN_LV_ADDITEM Warning W8075 .\\HB_FUNC.PRG 717: Suspicious pointer conversion in function HB_FUN_LV_ADDITEM ...

... ( TCHAR * ) cTitle );#endif}#pragma ENDDUMP now when #define UNICODE i got these Warning Warning W8075 HBFUNC.prg 61: Suspicious pointer conversion in function HB_FUN_FINDREPLACEDLG Warning W8075 HBFUNC.prg 62: Suspicious pointer conversion in function HB_FUN_FINDREPLACEDLG ...

... At the top of your C code place this line: LPWSTR AnsiToWide( LPSTR cAnsi ); thx for Answer. still got Warning Warning W8075 .\\HB_FUNC.PRG 1092: Suspicious pointer conversion in function HB_FUN_SETGRIDQUERYDATA but i have to use #define UNICODE to use Unicode Version so how to compile App where ...

... Warning W8069 .\\HB_FUNC.PRG 1090: Nonportable pointer conversion in function HB_FUN_SETGRIDQUERYDATA Warning W8075 .\\HB_FUNC.PRG 1091: Suspicious pointer conversion in function HB_FUN_SETGRIDQUERYDATA #define UNICODEHB_FUNC( SETGRIDQUERYDATA ){   #ifndef _WIN64      LPARAM ...

... Warning W8004 TEST1.prg 147: 'fRemoveSafely' is assigned a value that is never used in function EjectVolume Warning W8075 TEST1.prg 153: Suspicious pointer conversion in function HB_FUN_EJECTREMOVABLE as it are "only Warning" and CODE "seems" to work i can use it ... ...

... Warning W8004 .\\HB_FUNC.PRG 132: 'fRemoveSafely' is assigned a value that is never used in function EjectVolume Warning W8075 .\\HB_FUNC.PRG 136: Suspicious pointer conversion in function HB_FUN_EJECTREMOVABLE msvc 64 bit HB_FUNC.PRG(97): warning C4244: "=": Konvertierung von "BOOL" ...

... Warning W8004 FWEJECT.prg 190: 'fRemoveSafely' is assigned a value that is never used in function EjectVolume Warning W8075 FWEJECT.prg 196: Suspicious pointer conversion in function HB_FUN_EJECTREMOVABLE --- What is DismountVolume()? It is not a Windows API. CODE is in Sample as "Prototype" ...

... Warning W8004 FWEJECT.prg 192: 'fRemoveSafely' is assigned a value that is never used in function EjectVolume Warning W8075 FWEJECT.prg 198: Suspicious pointer conversion in function HB_FUN_EJECTREMOVABLE Try: BOOL fRemoveSafely; // = FALSE;BOOL fAutoEject; // = FALSE; hb_retl( EjectVolume( ...

... Warning W8004 FWEJECT.prg 192: 'fRemoveSafely' is assigned a value that is never used in function EjectVolume Warning W8075 FWEJECT.prg 198: Suspicious pointer conversion in function HB_FUN_EJECTREMOVABLE

... 112: Nonportable pointer conversion in function HB_FUN_XLBOOKSAVERAW Warning W8075 d:\\users\\jose\\desktop\\libxl-hbr\\source\\Libxlfnc.prg 319: Suspicious pointer conversion in function HB_FUN_XLBOOKSETKEY Warning W8075 d:\\users\\jose\\desktop\\libxl-hbr\\source\\Libxlfnc.prg 319: Suspicious ...

... 112: Nonportable pointer conversion in function HB_FUN_XLBOOKSAVERAW Warning W8075 d:\\users\\jose\\desktop\\libxl-hbr\\source\\Libxlfnc.prg 319: Suspicious pointer conversion in function HB_FUN_XLBOOKSETKEY Warning W8075 d:\\users\\jose\\desktop\\libxl-hbr\\source\\Libxlfnc.prg 319: Suspicious ...

... 112: Nonportable pointer conversion in function HB_FUN_XLBOOKSAVERAW Warning W8075 d:\\users\\jose\\desktop\\libxl-hbr\\source\\Libxlfnc.prg 319: Suspicious pointer conversion in function HB_FUN_XLBOOKSETKEY Warning W8075 d:\\users\\jose\\desktop\\libxl-hbr\\source\\Libxlfnc.prg 319: Suspicious ...

Thanks Cristobal.
The sentence now works in my standalone test but not my module.
Is there anyway to check where the linker is pulling hb_regex() from? It seems suspicious that I get an empty array when there is no match instead of NIL

I can´t see anything suspicious in your code. Perhaps the executable file was somehow corrupted. I would try to recompile with an irrelevant modification and try to run under another name on my client's installations.