🚀 go-pugleaf

Thanks for the information.

With that and a few hours trial and error I was able to get the
ClientDataSets working really well. The application can now create new
master and detail records (I don't use Master-Detail definitions on the
datasets but have 'rolled my own'), update the new data and then continue to
edit the new data with no errors.

This is better than a lot of applications based directly on ADO DataSets
(including some of my own) where master data often has to be saved before
detail records can be added.

If anyone is interested I would be happy to post details of the solution,
though with 20-20 hindsight and improved understanding I know realise that
the information was contained in the various articles and posts I had looked
at before. With the exception of Jet supporting the @@IDENTITY mechanism
that is.

Cheers
Bas

"Viatcheslav V. Vassiliev" <support@oledbdirect.com> wrote in message
news:43273953$1@newsgroups.borland.com...
> Access, at least Jet 4 through OLEDB/ADO, supports select @@identity.
> However it would be good to test how it works in multi-user mode (or with
> multiple TADOConnections to the same db) because of lazy writes
implemented
> in Access.
>
> //------------------------------------------
> Regards,
> Vassiliev V. V.
> http://www.managed-vcl.com - using .Net objects in Delphi for Win32 +
> ADO.Net
> http://www.oledbdirect.com - The fastest way to access MS SQL Server,
> MS Jet (Access) and Interbase (through OLEDB)
>