>>So what will be the advantage of having a new VFP autocrementing feature?
>
>Less code.
>

Mike,
Thanks for the response. My first thought was to ask you if one would lose the flexibility over the home-grown approach typically used now, bust as you suggest, if you don't like the built in version, the old way is still available. We will have two options for handling PK's in the future; typical of VFP, eh?

Pete

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