Rob, i dont disagree... But it should be visible to the browsing or searching user. If he wants to edit it, then a query should be done to see if possible or delay+update+allow...
cheers X > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Rob Cozens > Sent: Tuesday, April 26, 2005 16:30 > To: How to use Revolution > Subject: RE: another multi-user "solution"? > > Xavier, et al: > > > >In a server-client - the client doesn't touch the database. > Only sends > >updates to the server to queue up changes. This way, you > have no locks, > >no problems. Everyone accesses it. > > A server-client system eliminates the potential for data > collision; but you still need record locking so one user can > prevent others from changing the record she is currently > working on while she is working on it. > > Rob Cozens CCW > Serendipity Software Company > > "And I, which was two fooles, do so grow three; > Who are a little wise, the best fooles bee." > > from "The Triple Foole" by John Donne (1572-1631) > > _______________________________________________ > use-revolution mailing list > use-revolution@lists.runrev.com > http://lists.runrev.com/mailman/listinfo/use-revolution > _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution