>A mini application has 2 tables master/detail and the master table has
>amongst its columns an Auto-Incremental field. If all processes are done
>on the server one assumes the auto increment is updated accordingly.
>If the server is disconnected, e.g. local files are used, and new master
>rows are inserted 1) would the Auto-incremental fields continue to
>function?
>2) what would happen if a connection to the server is re-established
>and the Updatebatch method is called?
>3) would the master table re-assign new IDs to the auto-incremental
>fields or is some special processing required to handle such scenarios?

>One must consider the fact that there are 2 or more users,
>one disconnects, in the interim others have added new records,
>and continues data entry at home on his/her laptop/notebook,
>a day later the disconnected user reconnects. What happens?

>How does ADO / Delphi  handle this?

>If the briefcase model deals with this cleanly, then a nightmare has
>been solved instantly.

>> AutoIncremental fields could end up being broken when using the
>> Briefcase model. I had scenarios where it started renumbering even
>> though there were entries in the table, disconnected, worked locally and
>> the updated the server. What is the work around.
>> Access 2000, Delphi 5 Enterprise, ADO, Windows 98

>I just did some quick testing and when I call the UpdateBatch method, the
>autoinc
>field is always assigned a unique value.  Are you seeing it assign numbers in
>one
>client that have already been assigned in another client?

>Mark