>You've said that the improvements between some versions weren't enough,
>in your eyes, to warrant the upgrade. As far as I can see you could >continue to use whatever version you had at the time and not upgrade
>until you personally were ready to.
I currently develop in FoxPro DOS 2.6 and VFP6 on a daily basis and partially disagree with your assertion.
Several years ago, we asked, "To VFP or not to VFP?" and decided that the DOS product was sufficient for our needs and we knew it well. We've since revised our stance and have started migrating development efforts towards Visual FoxPro due to lack of third-party support for all things DOS. :)
Equipment vendors very rarely produce DOS based drivers. Sometimes an API is available and I can write my own drivers. So even though the requirements are fairly static, we are having increased difficulty in acquiring necessary support hardware.
Why would hardware manufacturers continue to produce drivers for DOS when the software vendor in question (Microsoft) no longer supports it? So even though we want to continue to develop in Fox DOS, lack of peripheral support forces our direction to Windows.
Though I have to admit that I'm excited about some of the features in VFP 8 and look forward to convincing mgmt. to buy it for me (and upgrade our Netware servers from 4.10 :D ).
---------
Single field, surrogate primary keys....because it's sexier!
Third normal form is more than just a good idea.