another multi-user "solution"?

[Rob Cozens]

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)