Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Security / September 2004

Tip: Looking for answers? Try searching our database.

Cannot access db on user's machine

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
JMorrell - 27 Sep 2004 18:57 GMT
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
Signature

JMorrell

JMorrell - 27 Sep 2004 19:37 GMT
I did another Compact and Repair Database again.  Now the beta tester can log
on, but the load procedure craps out at when loading a form.  For some
reason, the VB form info dies when loading.  

Incedentally, I loaded this onto yet another machine and everything works
fine.  It loads, I can write to the db, it saves, all the bells and whistles
work; even with multiple log ons.

Could it be the beta user's pc that's causing the problem?  If so, what can
be done about it; reload the app?

tia

> 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
[quoted text clipped - 16 lines]
>
> tia
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.