J
Jon Vaughan
I have a program that uses disconnected recordsets on the client side :
Here is the problem I have :
Client gets a dataset , say a customer table
Creates a new customer
Deletes this customer
Updates changes to server.
The server code detects that a record has been deleted via rowstate, takes
the new ID of the deleted record ( generated by the client side table via
setting autoincrement to true and setting the seed to the last ID + 1).
Now this causes 2 problems :
1.) It doesnt need to delete as it was only a client side record create and
deleted and therefore isnt on the sevrer.
2.) What happens if another user creates a record that is given the newly
created local ID that is the same as the one that im trying to delete.
Basically I have a problem with my distributed programming methodology. Can
someone point me to the right way to handle this ?
Thanks
Here is the problem I have :
Client gets a dataset , say a customer table
Creates a new customer
Deletes this customer
Updates changes to server.
The server code detects that a record has been deleted via rowstate, takes
the new ID of the deleted record ( generated by the client side table via
setting autoincrement to true and setting the seed to the last ID + 1).
Now this causes 2 problems :
1.) It doesnt need to delete as it was only a client side record create and
deleted and therefore isnt on the sevrer.
2.) What happens if another user creates a record that is given the newly
created local ID that is the same as the one that im trying to delete.
Basically I have a problem with my distributed programming methodology. Can
someone point me to the right way to handle this ?
Thanks