>Kevin... see comments inline.
>
>>>No conversion is necessary, unlesss you want to use some of the new features of VFP 8.0.
>>
>>I didn't think there was, seems you can do it without any intervention.
>
>Correct, except that there ARE certain 'behavioural' changes that might pose some inconvenience. Two that seemed to come up often are:
>1) LOCAL now requires a comma between memvars named.
>2) _INCSEEK replaces _DBLCLICK to control incremental search in listboxes and comboboxes.

The first one is ok by me, I've always done that.

The 2nd one will cause "slight" problems in my app, but shouldn't be too big an issue.

>
>>
>>>I am developing forms in VFP 8.0 Beta and running them in both VFP 6.0 & 8.0, so I can use the new IDE.
>>>
>>>We are going to skip VFP 7.0 and upgrade to VFP 8.0 in the spring.
>>
>>We may do this too, besides, VFP8.0 is more attractive than version 7, especially when you are currently using v6.0.
>
>If you have the VFP8 beta on hand and are using it, then this is a reasonable stratgey. But if you don't, and given the price of a VFP7 upgrade, you might want to consider buying it in the interim.
>I say this mainly as regards Intellisense. Using VFP7 to get used to that may be worth the price! It offers HUGE advantage yet takes considerable 'conditioning' to learn/remember/beat its foibles. The easier course will seem to be to turn it off, but that would be a big mistake!!!

Yes, I have the beta at the moment, and I'm using it to continue a v6.0 development. I have indeed turned IS off, due to it's presence, I know it has it's uses, but I'm a fast typest and find it keeps coming up with 2 ON's etc.etc. and it annoys me.

Kev