>>I bought some cool third party tools that allow me to build nice applications with VFP6. But with VFP7 I have some problems. So for now it's not too bad because I can still use VFP6.
>>
>>So if I have problems with these third party tools with VFP7 I don't see why I would'nt have the same problems with VFP8.
>>
>>But the catch is that I can't upgrade to VFP8 because I don't know if I'll have problems with those tools. And If I upgrade to VFP8 and have problems with those tools I can't go back to VFP6. Sure I could remove VFP8 (or can I from a legal point of view because at that point I upgraded to VFP8) and stay with VFP 7 or 6 or others below. But after losing some dollars doing the VFP8 test.
>
>Dennis,
>
>I might be wrong ofcourse, but it seems that your problem is caused by having a 3rd party tool but you did hesitate to understand the architecture of it. Isn't it true that 3rd party tools and/or frameworks can be bought with the codes in it?


I'm lucky enough to have all the source code to the third party tools that I bought. But for some tools there is no support for VFP7. So there's a good chance that I'll have to catch all the things that don't work. I'm not sure at this moment I want to do that because of the time factor and also that the clients already using apps made with these tools don't want to change their apps.

But the third party tools was given primarily as an example of things that can go wrong when upgrading from a version to another and when you're confronted to those contracts ties.