Updates in Access
Can multiple users make updates in Access simultaneously?
Software/Hardware used:
ms office
Software/Hardware used:
ms office
ASKED:
March 13, 2013 3:19 PM
UPDATED:
March 13, 2013 3:52 PM
Answer Wiki:
I have no idea what JohnKennedey is talking about. I open my access 2003 backend on the server directly nearly every day while I and/or my users have front ends open. I can make updates in the tables and changes to the queries. However, you cannot change the table properties unless all frontends are closed, or at least have no queries or forms open accessing the table in question.
All Answer Wiki Contributors:
Mlwonio 
90 pts. ,
TomLiotta 110,115 pts. ,
Michael Tidmarsh 14,000 pts.
90 pts. ,
TomLiotta 110,115 pts. ,
Michael Tidmarsh 14,000 pts. To see all answers submitted to the Answer Wiki: View Answer History.
In my experience with Access 2003 you had to make a second database which had remote access to the tables in the first database.
Multiple users could use this second database and through the remote access update data in the first.
You need to know how to separate your tables from the actual forms containing codes , that is, BackEnd (BE) and FrontEnd(FE). BE contains only Tables while FE contains forms with codes only. so in a N/W environment( make sure all the your computes that have privilege to access these Dbase file are configured on the same workgroup. And then set the server where the Dbase resides and apply some logics, which I can send you screenshots, and copy the Fe to all the N/w computers and link this FE to the Dbase on the Server. There are several ways of linking Fe to your BE. 1. on Access menubar there is Dbase Tool choose Linked Table Manager and locate where your Dbase file on the network(n/w)2.The second If you need I can send you screen shots.It is the easiest way of doing Data Entry in the world of s/w development bs it is easier to make changes on the forms (FE) without affecting the tables(BE)
In addition, remember the Dbase file on the server must be stored in Folder so as to set sharing properties, Ok?
Even without splitting into front & back ends, multiple users can update at the same time. But more than one user cannot edit the same record in the same table.
Even without splitting into front & back ends, multiple users can update at the same time. But more than one user cannot edit the same record in the same table at the same time. Either a warning icon will appear at the left that the record is already open for editing, and/or a dialogue will open to let you know that another edit is pending and offer some options. In any case, it is faster to have a back end with just the tables, and multiple copies of the front tend with all the queries and forms. Ust the Database Splitter tool to create separate front and back ends from your present file. Each front end can be linked to the backend files. Look under File|Get external data|Link tables. Any good Access manual will explain all this, and more, in great detail, with screen shots.
The reason why I prefer BE and Fe System because it allows multiple simultaneous transactions to happen within the system BUT the only challenge is that path leading to where the Dbase file is stored, that is, You can’t open or access the BE in the server , however this problem can be address in that if you want to access the BE then the user can start its FE and go to DESIGN VIEW AND PRESS FUNCTION KEY 11 ON THE KEYBOARD to access the BE and this one can take place at the same time even though very slow….Any feedback or reaction this can explain further…