>>John,
>>
>>In the Default Value of the ID field I put the code GenerateID("Mytable", "MyIndex") which calls a function GenerateID(). This function is kept in the same folder as the tables, although it COULD be added to the Stored Procedures.
>>
>>The function loads an ID table, looks for a record for 'MyTable' and defaults to the index 'MyIndex'. The record is locked, a value is incremented and the new value is used as the ID. With record locking I can be sure that only one user gets the next ID.
>>
>>And yes, this is always a Primary index.
>>
>>HTH
>>Barbara
>
>Barbara,
>
>Does putting the call to GenerateID() in the default value automaticaly add the new index value when you append a new record?

PMFJI- Yes. Automatically. Even in a browse.

>
>I use a seperate table and code to generate a unique index value for any table in the application. It sounds similar to the one you use except for the record locking (I have none at the moment).

If the app is multi-user, you will need to lock the record to prevent 2 clients from grabbing the same id before one has the chance to increment it.