Hi!
This is a change in the VFP7 language. Comma is required. This is because without comma syntax would cause conflicts with a new VFP7 feature to define type of the variable (for IntelliSense and for COM object interfaces).
BTW, I did never used syntax without comma, because it drops readability of the code...
>We upgraded to vfp 7.0 and immediatley compiled one of our larger applications to a vfp7 exe file and received 2 pages of syntax errors
>The compile and build of the exe in vfp 6 is error free
>The errors in VFP 7 were, missing commas, between local variable declarations
>eg.
>******************************
>LOCAL lnanswer, lncount llok
>******************************
> ^-missing comma
>
>At run time occasionally some of my users would report an erroneous error message that i was unable to trace to successfully
>Has any one else come across this situation
>Thanks
Vlad Grynchyshyn, Project Manager, MCP
vgryn@yahoo.comICQ #10709245
The professional level of programmer could be determined by level of stupidity of his/her bugs
It is not appropriate to say that question is "foolish". There could be only foolish answers. Everybody passed period of time when knows nothing about something.