>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.

I considered that, initially the tools began in VFP7 and were backward compatible to VFP 6. But with the improvements (particularly the UI) of VFP9, I decided to code for that as my base and moved to VFP9.

It was a decision to either take advantage of the new features offered in VFP9 or to ignore them and choose the lowest common denominator which typically is VFP6. I also wanted to use the TRY-ENDTRY error trapping -- that now limits it to VFP8. I liked the capability of the pageframe tabs on the right side and the rotation of text. Also, the new polypoints gave an improvement to being able to create a tab shape without a bitmap. Now the lowest common version is VFP9.

At some point we all need to move to VFP9. If we stay at the old versions and do not support VFP by buying the upgrades at some point MS decides that the revenue stream is not enough with the few developers that are upgrading. I decided that these utilities would be at VFP9 to encourage the migration to VFP9 in order to use them.



>I would interested to know what are the percentage of developers that develop in which versions.

I would too -- we need to support the development of the VFP versions as a community to ensure the continued development of VFP by MS.