Mike,

>> So what will b>e the advantage of having a new VFP autocrementing feature?

> Less code.
>
> Bottom line is right there, if I can remove complexity from my
> applications by utilizing what is in the language, I will. Same with the
> grid hightlighting, or the tab positions. I'll just go to what will be the
> easiest to maintain, an in that case, setting a property in the database
> will but much better than setting the field's default to a function,
> keeping the function available, and making sure the table that goes with
> it is existent and available.

True for most developers. However, some of us don't have to write
additional code to generate the PK because the function is part of our
framework. Setting proterties in a metatable is just about the same
amount of work as setting properties in a database.


> Thats not to say I'm going to assume that the new features meet everyone
> of my requirements, so I'll test it hard. But after it passes the test,
> its in like Flynt.
>
> I imagine it will perform better too, and most likely more reliablly
> too. But we'll see.

Flexivility and reliability are two reasons that I stated why I will keep
my alternative in place. I also ventured that the VFP AutoIncrement feature
should ourperform my function but it was not a major argument for
switching over.

Daniel