I would highly recommend NOT changing a project from 5.0 to 6.0. I'm sure it's not so bad if you are starting a new project from scratch, but we are having no end of problems in 6.0 with code that was perfectly content in 5.0.

We had to switch due to a 5.0 printing bug we couldn't work around, but I deeply regret having to make the change.



>There's lots of disagreement here over the stability of VFP 6. I find it less stable than VFP 5.0, build 415 (the last release of 5.0). At the very least you will need to do complete regression testing if you upgrade to 6.0. You will probably have to work around some of the new bugs. There will be less documentation available on bugs than there is for 5.0 because it takes a while for MS to document everything in their knowledge base.
>
>There's a patch for VFP 6.0 coming out, probably this spring. If you don't plan on releasing your application until well after that you may be able to take advantage of it. You should also take into consideration whether there are any features of VFP 6 that would be particularly useful for your project.
>
>>I have been working on a package for a little over a year, when I arrived at this particular site they were using VFP3, I immediately
>>upgraded them to VFP5 the Professional Version, since my project is not complete and is only released in the testing mode is there any reason to hold back from upgrading to VFP6 or Visual Studios.
>>
>>John G.