CPGDeveloper
Board Regular
- Joined
- Oct 8, 2008
- Messages
- 189
Hello~
I've created and administer an Access DB application -- 20+ end users -- split db -- each user has a copy of an accde executable file on their desktop, while the back end is on a network server. The front end is programmed to shut down automatically @ 8pm every night.
Once in awhile (every 3-ish weeks or so), the back end will "freeze" -- nobody is in the db, there is no lock file, but the database can only open read only, no record can be edited, and no record can be added. This only seems to happen first thing in the morning -- as people start their day and start to use the db. It has yet to happen in the middle of the day.
This does seem to clear itself up if I give it a couple of hours, but of course the business cannot wait a couple of hours. When this happens, I make a copy of the back end, and re-issue a front end linked to this copy and make that our new back end.
Is there a way to prevent this? I do compact and repair the back end once a week or so -- do i need to do that every day? I am not considering simply creating a new back end every week or so as a preventative measure. But is there something else that might be going on? Is it something in my coding that might be causing the back end to 'lock' like this?
I've created and administer an Access DB application -- 20+ end users -- split db -- each user has a copy of an accde executable file on their desktop, while the back end is on a network server. The front end is programmed to shut down automatically @ 8pm every night.
Once in awhile (every 3-ish weeks or so), the back end will "freeze" -- nobody is in the db, there is no lock file, but the database can only open read only, no record can be edited, and no record can be added. This only seems to happen first thing in the morning -- as people start their day and start to use the db. It has yet to happen in the middle of the day.
This does seem to clear itself up if I give it a couple of hours, but of course the business cannot wait a couple of hours. When this happens, I make a copy of the back end, and re-issue a front end linked to this copy and make that our new back end.
Is there a way to prevent this? I do compact and repair the back end once a week or so -- do i need to do that every day? I am not considering simply creating a new back end every week or so as a preventative measure. But is there something else that might be going on? Is it something in my coding that might be causing the back end to 'lock' like this?