Everyone, OK I wrote a test program with the offending line of code. It is wrapped in a dummy class just we can test the line as is. This one doesn't error using my old xHarbour ver. 1.2.3. James /*Purpose : Test compile to test error generated ...
... you very much for your response, however I'm getting the following compilation error: Error E0030 Syntax error "syntax error at '@'" Offending line: @ 1, 1 PRINT TO oPrn IMAGE cImage SIZE 7,9 INCHES NOTRANSPARENT STRETCH I'm using FW 16.03, any ideas ? Thank you very much !
It's hard to say. I cannot recreate the error at my end and no error log is generated. I guess I'll sprinkle the code with some msginfo calls and see if I can pinpoint the offending code.
Thanks again, Randal
Antonio Linares wrote:Randal,
If you don't call WinExec() then there is no error ?
... error at 'FUNCTION'" "c:\dev\testui\source\uiwindow.prg(3495) Error E0030 Syntax error "sytanx error at 'FUNCTION'" the offending lines are those: DLL FUNCTION keybd_event( bVk as _INT, ; bScan as _INT, ; dwFlags as ...
... the following compile error: c:\fwh\source\function\errsysw.prg(24) Error E0004 STATIC declaration follows executable statement The offending line is: //----------------------------------------------------------------------------//static bUserAction//----------------------------------------------------------------------------// ...
... totally new font with a different facename ( roman or some other ) and use that font exclusively only for RBBTNS. Then we'll be more clear if the offending code is in RBBtn or somewhere else.
Antonio, Great! There's only one Unresolved external error left. Here I attached the offending code. BTW, I am not very good in Spanish. :) Thank you, Jose Turbo Incremental Link 5.69 Copyright (c) 1997-2005 Borland Error: Unresolved external '_HB_FUN_WBROWSE' referenced ...
... I added a "placeholder" variable ph := IIF(.... to all of them and deleted one at a time and compiled to find which two lines were offending. REDEFINE BUTTON oBtn1 ID 1026 WHEN nPermis < 4 ACTION ; ...
... one is causing you the problem. At times I have had to resort to just start at the top of your Update and rem out each value til you find the offending line. Rick Lipkin
... ? So i suppose that this is also now the case. Anyhow , i will include your code (with a tracelog) , so that i can see which line produces the offending code. Many thanks , Frank Demont
... from ISO-8859-1 to ISO-8859-15, which is needed to be able to represent all characters in the current Swedish collation. Though it turns out these offending three chars are not part of the Swedish alphabet. So here I'm finishing and letting others to fix the rest if there is any. [INCOMPATIBLE] ...