>>>>>>>Hey Guys!
>>>>>>>
>>>>>>>Was the GKKCompare-1.0.zip compiled in VFP 9.0 ??
>>>>>>>
>>>>>>>When I run it in VFP 8.0 SP1 I get a file too large error.
>>>>>>>
>>>>>>>Thanks!
>>>>>>>
>>>>>>>Tommy
>>>>>>
>>>>>>I do too.
>>>>>
>>>>>At least it's not me this time!!! (grin)
>>>>
>>>>Even though the latest version of VFP has alot of great new stuff. I try to develop tools and utilities with a little backwards compatibility. Therefore more developers can find use with. Over the last few years I have been work on the LifeCycle Build utility (now nearing 2.0 beta) and I have always made sure it would run vfp 6.0 and above.
>>>>
>>>>I would interested to know what are the percentage of developers that develop in which versions.
>>>
>>>My philosuphy is totally different, because the fewer people who upgrade, the sooner VFP will be killed by MSFT. So when I create a new utility or function, I focus on making it work in the newest version, and don't care about older versions at all.
>>
>>If we are talking about an end user application then I agree. But for developer end utilities, I try to make it avaliable to as many as possible.
>
>I am talking about developer utilities. Developers who don't upgrade, are actively helping VFP to be killed. I see absolutely no reason for not upgrading.
>
>Some argue that it's the cost of upgrading that hold them back. Unless you live in a country where the wages are extremely low, the upgrade will pay for itself in a month or two. With all the new features, especially intellisense, try-catch error handling and the new report engine, not upgrading is simply stupid, in my mind. If your boss is not willing to invest in a more modern tool, change boss! I would never work for a boss who is too cheap to buy me up to date tools for my every day work.
>
>Some argue that they are afraid that their application will nor work in newer versions. The compatibility history of VFP is unique, personally I have never used more than a few hours to get my application to work in a new version. And most of the changes I have been forced to do, have been to fix my own typos, because newer versions have more strict syntax checking.

In way you express it, I agree with you. As a developer I too like to have the best tools at my disposal. But from time to time I come across a client that don't want to risk the upgrading.