Wincanton_Kid
New member
- Local time
- Tomorrow, 04:52
- Joined
- Apr 3, 2012
- Messages
- 2
I have a problem with a database (no surprises there).
The setup is that we have a proprietary programme (*.exe) from a now defunct company that uses a shared Access 2003 mdb as the backend - fortunately, it's still working fine.
We also have another Access 2003 mde frontend running on a runtime which links to one of the tables to read the data, neither of the frontends or the backend have been updated since last year (aside from data changing in the tables).
Since the middle of February, we have had a problem with the Access mde taking exclusive access of the backend database (symptoms: not creating a lock file and the proprietary programme erroring with an "unable to write to table" error).
We have checked the permissions on the folder and have checked that all the Access databases involved should be opening as shared. We have not changed anything to cause the issue and the only thing we can think of is the heap of MS Office updates that came through from Microsoft around the time the problem started, though we can't see anything in them that would cause this problem.
Question: Has anyone else had this issue, or does anyone have any ideas while I still retain a shred of sanity?
Many thanks
David
The setup is that we have a proprietary programme (*.exe) from a now defunct company that uses a shared Access 2003 mdb as the backend - fortunately, it's still working fine.
We also have another Access 2003 mde frontend running on a runtime which links to one of the tables to read the data, neither of the frontends or the backend have been updated since last year (aside from data changing in the tables).
Since the middle of February, we have had a problem with the Access mde taking exclusive access of the backend database (symptoms: not creating a lock file and the proprietary programme erroring with an "unable to write to table" error).
We have checked the permissions on the folder and have checked that all the Access databases involved should be opening as shared. We have not changed anything to cause the issue and the only thing we can think of is the heap of MS Office updates that came through from Microsoft around the time the problem started, though we can't see anything in them that would cause this problem.
Question: Has anyone else had this issue, or does anyone have any ideas while I still retain a shred of sanity?
Many thanks
David
Last edited:
