On Mon, Sep 22, 2008 at 7:46 PM, Klaus Major <[EMAIL PROTECTED]> wrote: > Hi all, > > this is a bit off topic, but maybe someone can give me some helpful hints. > > Is someone of you working with databases with multiple users? > If yes, how do you handle "concurrent transactions"? > > I mean how do you solve the possible overwriting of data when both users > work with > cursors and are allowed to update data and how do you update a cursor (on > the fly?) > when its data may have been updated?
I did one project like this and I solved it by having a table that recorded when a user was accessing a record. Another person could look at that record, but would get a warning that the record was already being used, and the "Save" button was disabled. The only problem was if the first user didn't log off or crashed, so I implemented a time-out feature for that. Cheers, Sarah _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
