I have a shared front end database with users using XP and 2000. Database was originally developed in 2000. I was switched over to XP about 1-2 months ago, and have been maintaining it in XP.
About 2 weeks ago, XP users could not open the database. They would not receive a runtime error - the database would open and the Access error message would appear. (The one that prompts you to send a report to MS). If a user with 2000 would open the database, the Switchboard would open with the label and one button showing, nothing else.
When I tried stepping through the code with XP, I did not receive any errors and the Switchboard form then opened - no error. If I closed the db and opened again - no error. I restored the front end from a dev copy and checked it before I went home at night and the error was back.
I ended up creating a new front end for the XP users by importing everything into a blank XP database. I also rebuilt the Switchboard using XP. So far, the users have not (knock on wood) received the error again.
Has anyone ever experienced anything like this? I would like to know what caused it if anyone has any suggestions. I have not been able to get the error/situation to recreate itself with test copies. I also could not find anything on MS or this website.
Thanks, Janel
About 2 weeks ago, XP users could not open the database. They would not receive a runtime error - the database would open and the Access error message would appear. (The one that prompts you to send a report to MS). If a user with 2000 would open the database, the Switchboard would open with the label and one button showing, nothing else.
When I tried stepping through the code with XP, I did not receive any errors and the Switchboard form then opened - no error. If I closed the db and opened again - no error. I restored the front end from a dev copy and checked it before I went home at night and the error was back.
I ended up creating a new front end for the XP users by importing everything into a blank XP database. I also rebuilt the Switchboard using XP. So far, the users have not (knock on wood) received the error again.
Has anyone ever experienced anything like this? I would like to know what caused it if anyone has any suggestions. I have not been able to get the error/situation to recreate itself with test copies. I also could not find anything on MS or this website.
Thanks, Janel