There are best practices for multi user apps with Access.
Normally you can split the database and keep the tables in a common back end in a commonly mapped network drive, and then give users a link to a front end stored on a network drive, OR give each user a copy of the front end. The users open the common front end which accesses the common back end, or their own copy of the front end. The problem with the second solution is that you have to get each user to manually save over the old front end when you have an update of the new front end. With the common front end, the users' each have a shortcut on their desktop, and they don't even need to know updates are being made to the front end.
If you want to develop, take a copy of the common front end and put it on your desktop. Then paste the revised front end to the network folder in the evening.
Developing the back end can be done on the fly, but be careful of making substantive structural changes when users are working.
Did any of that help?