Quote:
|
Originally Posted by NeoSparky
the access file is nothing more than a file in the setup you described. Yes you can edit the file in 2 locations but if your making any change other than database related you will encounter the old who saved last wins scenario.
|
Exactly, and since the 2 clients cannot practically be synchronized, he will need some type of (sql?) server to handle table locking etc.
Any idea as to what the easiest way would be?
(I'm also thinking: it could be possible to use a locking file that shows who's editing. If the file exists the other is editing, and the client needs to wait. The file dissappears and the client can edit the database..... a mutex aproach
But I'd rather have a more elegant solution)