Originally Posted by Minty
Any chance of trying to open the database on another machine ?
It would remove the possibility of a local windows/office/access issue.
Do you have a working backup someone else could try opening?
This is a split database - I have opened the front end on several different machines and the problem is the same. I'm pretty sure it's not a local windows/access issue.
The most recent backups behave the same way, regardless of which machine is used.
I just had a thought - this did not start happening until I added a hidden idle timeout form triggered by an autoexec macro.
Could this have caused this problem?