Splitting DB's

[vnfoster]

I hope this is a quick question with a quick solution.

I have created a DB, that has 10 users, 5 are on site and the other 5 of off site at various locations. In order for everyone to have access I have put the DB on a Network folder, being able to access the current DB is contingent on being plugged into the network, which has a tendency to go down or run reallllly slowly for those users offsite. I think the solution might be to split the database so that off site users can still have access if the network is in accessible for awhile. My question is this:

If the network goes down and my offsite users are using the front end database, will the backend automatically update when the network is back online. If not can anyone help me think of a work around. We are not allowed to use external hard drives.

Thank you so much in advance.

 

[Frothingslosh]

First off, any time you have multiple users using one database, you should split the database. Access does not work well at all with multiple users using the same forms and procedures at the same time.

Second, Access does not do asynchronous record updating. While it's certainly possible to write code to use an alternate (local) backend and even to upload any records saved in that backend once you connect to the primary backend, you run into all sorts of problems. What do you do if two people alter the same record? What if someone deletes a record someone else needs to update?