>> Sacarsm aside, you may have a need for a native AutoIncrement function
>> but my friends and I certainly don't.
> That's nice. I don't plan to use it, either, because I have an alternative
> in place, but I can surely tell you I _would_ have used it in the
> beginning if it had been available, and one does hold out hope that VFP
> will always be gaining new developers who might appreciate the feature.
> As for major...yes, it is. It's been a constantly requested feature ever
> since I've been in the community and it's one of the most frequently asked
> questions on newsgroups when people are coming to VFP from other backends
> that support it.

I would define a major feature to be a feature that is useful to the
majority of the developers using a product. AutoIncrement doesn't fit the
bill IMO.


>> In my opinion, saying it's a major feature is almost equivalent to saying
>> that we won't get anything really useful in the next version.
> Every new version of VFP has been previewed a bit at a time. VFP 7 started
> out with just Intellisense, If I remember correctly. It seems MS is damned
> if they do show teasers ("Is that all there is?") and damned if they don't
> ("Oh, no! VFP 7.0 is the last version!").

My point were:
1. AutoIncrement is a minor feature.
2. The vastt majority of the potential purchasers of VFP8 (us developers)
already own a prior version of the product
3. Most developers have an alternative to AutoIncrement.
I for one do not typically upgrade a product unless it allows me to do some
things I couldn't do before.

I expect to see much more useful features as we get closer to the launch date.


> If you have a feature you would find helpful, please make a request. But
> just because you don't care about it, doesn't mean someone else doesn't.

I suggested overloading and the friend keyword years ago.

Daniel