G
Guest
I'm dba for a new db (beta version) with User Level Security. There is a
user who is working through this beta version who comes up with suggestions
for improvement, and/or logic errors. The data tables sit on an SQL Server
and the 'front end' links to them.
After a recent modification to the db, the user can not access the db (which
is copied to a CD and then installed to her machine). On her machine, I
can't open the db, but I can on mine (same file). I've tried a 'Compact and
Repair Database...' without any luck. When she (or I) click on her desktop
icon which is a shortcut with the .mdw file, it brings up nothing (Access
opens, but the custom switchboard doesn't) . When I try it again, it creates
an error log, which I assume is telling me that there is already a lock file
on her machine. Deleting both of these lock files does nothing to fix the
problem.
Somehow, the file became corrupt. What should I be looking for to fix this
problem? There is last week's backup copy to revert to, but I would prefer
to not go that route.
tia
user who is working through this beta version who comes up with suggestions
for improvement, and/or logic errors. The data tables sit on an SQL Server
and the 'front end' links to them.
After a recent modification to the db, the user can not access the db (which
is copied to a CD and then installed to her machine). On her machine, I
can't open the db, but I can on mine (same file). I've tried a 'Compact and
Repair Database...' without any luck. When she (or I) click on her desktop
icon which is a shortcut with the .mdw file, it brings up nothing (Access
opens, but the custom switchboard doesn't) . When I try it again, it creates
an error log, which I assume is telling me that there is already a lock file
on her machine. Deleting both of these lock files does nothing to fix the
problem.
Somehow, the file became corrupt. What should I be looking for to fix this
problem? There is last week's backup copy to revert to, but I would prefer
to not go that route.
tia