VFP8 and "Syntax Error" while opening form

[vazagothic]

I've experienced a weird behaviour while opening a form under VFP8 (the same form work flawlessly under VFP6)

When I open the form under VFP8 I receive a message:
"Syntax Error"
no other expanation is given.

I've looked through all object properties, but I didn't
find anything out of order.

I can modify the form and save it without any problems.
But the next time I open it - "Syntax Error" strikes back.

Did anyone else experience similar behaviour and solved the mystery ?

 

[DSummZZZ]

Do you have any controls whose RecordSource is set to SQL?
If so, you may need to try this setting:

SET ENGINEBEHAVIOR 70


-Dave Summers-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm

 

[vazagothic]

Nope, I don't use SQL in RecordSource .. only Alias.

I've rechecked the form (and the parent classes).

No change.

 

[ramani]

Hi

It is likely that you have a macro and that macro is not valid at the time of starting the form. It may be available later on.

YOu can capture the error probably by adding suitably code in the ERROR event of the form.



____________________________________________
ramani - (Subramanian.G)

http://winnersoft.coolfreepages.com/

 

[vazagothic]

So why does VFP6 opens the form w/o an error ?

And the ON ERROR won't work, since I try to edit the form, not run it

 

[rgbean]

There were many situations where the syntax was "tightened" in VFP 7 & 8. This was usually due to new features that were added that make the old (incorrect) syntax now illegal. e.g. This is "valid" in VFP 6.0, but not in 7 & 8.

LOCAL aa, bb  cc, dd

The missing comma wasn't flagged before, but it is now!

Rick