Colin,

You can start developing in VFP9, not using the new stuff (language enhancements) and still compile in the older version. This way you can get comfortable with the IDE enhancements and take advantage of the productivity tools, but the code is not yet updated. There are several settings that let the new version mimic older versions as not to break your code until you can test the individual areas and update them (you can turn these on/off just where needed).

Moving to SQL server will take a lot more work and is dependant on how flexible your current structure is. If you use a class or object to handle your data request, its not too bad you can make the changes in one are of code and upsize your data and start testing. If your data is done locally throughout your app, then you need to change it everywhere and should move to the model I just mentioned first.

Moving to SQL would make the transition toi .Net easier, but either moving to .Net is a big move.

Bob

>Bob
>
>Thanks for that - don't use stored procedures - have had a look at upgrading to VFP9 - looks great but it would a long period of parallel running to iron out differences - that is unless you can convince me that VFP9 is totally backwards compatible
>
>I have already floated $400,000 redevelopment and a timescale of 4-5 man years to redevelop the app to another software platform - big hit for a company to take - but it is a very large app with about 8 smaller apps linking in to it - system is installed in UK in Queens NY and shortly in Frankfurt and because of local market differences the UK and NY systems are already poles apart after only a couple of years running in NY
>
>How difficult is it for an experiences VFP programmer to migrate to .Net?
>
>Thanks
>
>Colin
>
>
>>Moving to the VFP9/SQL model would be a moving in a direction which would be easier to migrate to .Net down the road if you need to, especially if you use stored procedures. Either way, you should really move to VFP9, not that painful from 6 and higher.
>>
>>
>>
>>Bob
>>
>>>Out of interest we still use VFP6 with one app in VFP9 - we dipped our toes in the water with VFP7 and hated it so stayed with VFP6 which does all we want - I am advised however that should I wish to move to a SQL backend I would be well advised to upgrade to VFP9 - what do you think and are the benefits to be gained from moving to SQL worth the hassle when the system is as stable as any constantly developing environment can be?