M
Matt W
Good afternoon. I've got a user running Access 2002 SP3 on a Windows XP
machine who receives an error that Microsoft Access couldn't find file
C:\Documents and Settings\<profile>\Application
Data\Microsoft\Access\system.mdw when trying to open a database stored in
C:\Documents and Settings\All Users\Desktop.
Other users can open the mdb without issue.
This user can open a copy of this database on another machine in the same
conditions with no issues.
The system.mdw file exists in the folder that Access says that it can't find
the file in, and renames itself in increments (system1.mdw, system2.mdw, etc.)
I have done the following:
Repaired and reinstalled Office.
Renamed the local profile for the user.
Re-registered DAO with regsvr32 msjtes40.dll.
Copied a system.mdw file from another location and placed it in C:\Program
Files\Common Files\System, then created a shortcut to the db pointing to this
..mdw file, same error.
Granted the user local admin rights. This produced a new error, which
states that the VB Project is corrupt when she tries to open reports in the
db.
Again, others can open the db just fine on the machine, just not this user,
who can open a different copy of the db just fine on other machines. One odd
thing about this user that I've noticed is that every time that she opens
Access it opens the new user identification dialogue, prompting for a name
and ID to identify her with.
Any suggestions?
machine who receives an error that Microsoft Access couldn't find file
C:\Documents and Settings\<profile>\Application
Data\Microsoft\Access\system.mdw when trying to open a database stored in
C:\Documents and Settings\All Users\Desktop.
Other users can open the mdb without issue.
This user can open a copy of this database on another machine in the same
conditions with no issues.
The system.mdw file exists in the folder that Access says that it can't find
the file in, and renames itself in increments (system1.mdw, system2.mdw, etc.)
I have done the following:
Repaired and reinstalled Office.
Renamed the local profile for the user.
Re-registered DAO with regsvr32 msjtes40.dll.
Copied a system.mdw file from another location and placed it in C:\Program
Files\Common Files\System, then created a shortcut to the db pointing to this
..mdw file, same error.
Granted the user local admin rights. This produced a new error, which
states that the VB Project is corrupt when she tries to open reports in the
db.
Again, others can open the db just fine on the machine, just not this user,
who can open a different copy of the db just fine on other machines. One odd
thing about this user that I've noticed is that every time that she opens
Access it opens the new user identification dialogue, prompting for a name
and ID to identify her with.
Any suggestions?