>IMO, little continuity certainty !! New Releases, new environment comes and/or the software supplier decide to change completely his framework (or stuffs like that)..
>
>Humm.. I passed through this situation many, many times.. How to deal with this ?
>
>Claudio

I don't understand your point. If a DLL works with VFP8 and with Windows, what do you care what the supplier does with it in the future? You buy it, you have it, it works for you now and it will still work in that environment in the future.

If you are talking of a Framework, I use a commercial VFP framework. It does certainly change, with frequent upgrades, improvements and bug fixes. None of that is suppossed to break any of your code, as long as you subclass into an intermediate layer that insulates you against any unwanted changes in the new version of the Framework. I could still be using the yr 2000 version of that Framework if I wanted, as I could still be using VFP6 and be happy with it, if I did not care for the newer capabilities.