Hi Haile,
I highly recommend that you fix the select statements and remove SET ENGINEBEHAVIOR 70 as soon as possible. SET ENGINEBEHAVIOR 70 may result in wrong data, that's why they changed the SQL engine, and the reason why they included the command SET ENGINEBEHAVIOR 70/80. Consider SET ENGINEBEHAVIOR 70 as an emeergency "band aid", not as a permanent fix!
>I have just migrated all my files from vfp 6.0 to vfp 9.0. The change went on smoothly except for 2 modifications I made: included "SET ENGINEBEHAVIOR 70" in the start up program and placing commas between explicitly defined variables in my programs (e.g. PUBLIC var1, var2, ... etc).
>However, after compiling my project into exe, the exe file cannot run on workstations that don't have vfp 9.0 installed on them. The start up program is the same that I use on vfp 6.0 and used to work. Does the READ EVENT command still work in vfp 9.0? Here is the main start up program:
>
>
>CLOSE TABLES ALL
>CLOSE DATABASES
>
>SET EXCL OFF
>SET TALK OFF
>SET DATE TO BRITISH
>SET CENTURY ON
>SET MARK TO
>SET DELETED OFF
>SET REFRESH TO 10,5
>SET LOCK ON
>SET BELL OFF
>SET ENGINEBEHAVIOR 70
>
>PUBLIC gcoldfilter, pvUsername, PvUsercode, pvItemopen, pvCount, pvEnrol_date, pvDate_inf, pvlast_visit
>
>pvUsername = ALLTRIM(SUBSTR(SYS(0),(AT("#",SYS(0))+1)))
>pvItemopen = 1
>gcoldfilter = ""
>pvEnrol_date = {}
>pvDate_inf = {}
>pvlast_visit = 0
>
>CD "\\mtwapa2\data\data\Database Management System\"
>
>OPEN DATABASE (CURDIR() + 'Databases\mtwapa')
>
>WITH _VFP
> .VISIBLE = .F.
> .CAPTION="IAVI Database Management System"
>ENDWITH
>
>_SCREEN.Icon = (CURDIR() + 'Other Files\iavi Icon.ICO')
>
>DO FORM (CURDIR() + 'forms\log form.scx')
>READ EVENTS
>
