>>I found the following in the VFP8 beta Help:
>>"Visual FoxPro does not manage gaps in generated sequences. Gaps can be caused by reverting an appended or inserted record or by failing to update the base table and so on. In all cases, the unused value is lost, and the next generated value remains the same as if the append or insert operation succeeded.".
>>
>>I interpret this to mean that the feature is useful for SURROGATE (primary) keys and cannot be used - at least practically - for an 'actual' (i.e. non-surrogate) key field.
>>
>>I don't know for sure, but I doubt that SQL Server or ACCESS handle this much differently.
>
>For SQL and Oracle this is correct. I could care less about Access < bg >.

The part about reusing gaps?

In SQL Server you can reuse gaps in identity fields caused by deleting, etc. with SET IDENTITY_INSERT ON.