Re: Saving A database to the desktop
- From: Steve Schapel <schapel@xxxxxxxxxxx>
- Date: Sun, 28 Sep 2008 10:00:44 +1300
Ram,
Certinly you could have multiple users using the application independently on their local machines. The problem arises when any data changes made by one user will overwrite the existing data on the server... see what I mean? User A and User B both get a copy of the database to use locally. User A enters or edits some data, and then re-submits his copy of the database to the server. In the meantime, User B is editing data on his local copy. Then when he re-submits his copy of the database to the server, it overwrites User A's work.
Or have I missed your meaning?
--
Steve Schapel, Microsoft Access MVP
ram wrote:
I thought they multiply users would be able to drag it to their respective desktop. Would you suggest a different soultion?.
The user experience slowness when ever they try to down load something from the share drive.
- Follow-Ups:
- Re: Saving A database to the desktop
- From: ram
- Re: Saving A database to the desktop
- References:
- Saving A database to the desktop
- From: ram
- Re: Saving A database to the desktop
- From: Steve Schapel
- Re: Saving A database to the desktop
- From: ram
- Re: Saving A database to the desktop
- From: Steve Schapel
- Re: Saving A database to the desktop
- From: ram
- Saving A database to the desktop
- Prev by Date: Re: Saving A database to the desktop
- Next by Date: Re: Saving A database to the desktop
- Previous by thread: Re: Saving A database to the desktop
- Next by thread: Re: Saving A database to the desktop
- Index(es):
Relevant Pages
|