>> Upgrading to 7 is the key. The only developers that will upgrade are those that either use the product or are part of teams that are using the product. There will be very little influx from other sources. If there is an influx, it will be very insignficant. <<

This is correct, developers need to upgrade to VFP 7.0. The Fox team is and will be measured by the number of developers who upgrade to VFP 7.0 or MSDN subscriptions, that is what determines the future of VFP more than anything else.

>> In my opinion, and I know this is an opinion shared by others, a way to help ensure upgrades to 7.0 is to add things like the grid-row-highlight planned for Toledo in a service release of 7. Perhaps adding the auto-incrementing keys would be a good step too. Again, if folks don't upgrade to 7, there very well may not be an 8. <<

This will not happen, service packs are for important bug fixes only and are not for adding new features. There is no service pack announced for VFP 7.0 because it is a very stable version, but if and when there is one, you will not see features like this added, only in the next major release. If you don't think the very long list of great new features of VFP 7.0 is not worth the upgrade and only adding a grid property is a reason to upgrade, then I think that logic is flawed. It appears this comment is an indirect way of trying to convince the Fox team to add this feature to a service pack because you want it, not because you truely feel VFP 7.0 is not worth an upgrade because I know you are too smart to conclude that. So this comment and thinking is actually harmful to the efforts of myself and the FoxPro commununity trying to convince developers to upgrade to VFP 7.0 now because of all the great new features and because it is a more stable version than any previous release.