Yep, going from C# to VFP is more dangerous in that respect (at least for me). The ";" at the wrong place in VFP can take the next line into consideration when it shouldn't.


>That is exactly what happens to me when I switch between VFP and Delphi. What's worse is that I don't even see the problem when it happens since the ';' works the opposite of each it does not necessarily generate an error...
>
>
>>>>>One reason I prefer C# is that it is different enough from VFP syntax so I don't get confused when jumping between the two. VB.Net is a little too similar and (another reason) is that I've done plenty of ASP with VBS and I hate VBS. Just having to add Then for every If (and I always forget) irks me.
>>>
>>>If it will help you over the hump, you can use THEN in your VFP code for IF blocks, it's allowable syntax. <g> (I prefer C#, too)
>>>
>>>I know that. I even tried it a couple of years ago when I was doing plenty of ASP+VBS. Only lasted less than a day. It looked so unnecessary and unnatural <g>. So I got used to then in VBSonly. Still forget it once in a while and I still do some ASP+VBS at work (unfortunately I still have to).
>>
>>My only problem between switching between VFP and C# is ending lines with a ";" at the wrong time. <g>