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 / Multiuser / Networking / August 2005

Tip: Looking for answers? Try searching our database.

Corruption problem

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Bill - 12 Aug 2005 04:13 GMT
Hi all.
I have a multiuser database distributed over a windows p2p network. This has
worked fine for 3 years. But my problem is this.......Every once in a while
the backend corrupts and needs to be repaired. This is not a problem in
itself but the lock file always stays in a state that says users are still
in the system and the lock file cannot be deleted until I reset the server
where the file resides.( I have another table in another database, which
when a boolean field is checked (yes) then the frontend(s) will close after
alerting the user that a problem exists). So the users are kicked out of the
system yet the lock file stays in the same state as when the backend
corrupted.
So my problem is my inability to delete this file so that I can compact and
repair the database.
Is this by design? Is there a way around my problem of having to reboot the
server to free the lock files state and delete it?
Please help. As I wrote code that closes everyone out, deletes the file and
compacts the backend, then allows users access again. But it will not work
because of my inability to delete the lock file unless I reboot the server
where the backend resides.

Help, help, help
Alex Dybenko - 12 Aug 2005 08:01 GMT
Hi,
if you mdb is locked - then it is opened by somebody (btw - could be
antivirus for example). you can try to discover this using this info:
http://www.mvps.org/access/general/gen0034.htm

Signature

Alex Dybenko (MVP)
http://Alex.Dybenko.com
http://www.PointLtd.com

> Hi all.
> I have a multiuser database distributed over a windows p2p network. This
[quoted text clipped - 24 lines]
>
> Help, help, help
Bill Taylor - 12 Aug 2005 13:30 GMT
Alex,
I have opened the ldb file and manually closed the front end connections to
close out all users. Sometimes the users that are shown in the lock file are
not in the database at all. So my problem is not that users have the
database open. As stated earlier...... All people are closed out, and the
lock file remains. My mdb is locked and yet nobody has it open. In fact,
nobody can have it open because it is corrupt and will not allow access.
Help, help, help
> Hi,
> if you mdb is locked - then it is opened by somebody (btw - could be
[quoted text clipped - 34 lines]
> >
> > Help, help, help
Alex Dybenko - 13 Aug 2005 10:52 GMT
i think you can get a filemonitor at www.sysinternals.com, and then check if
file really accessed by any process.
Also you can try to find out which PC cause corruption, by taking out
one-by-one

Signature

Alex Dybenko (MVP)
http://Alex.Dybenko.com
http://www.PointLtd.com

> Alex,
> I have opened the ldb file and manually closed the front end connections
[quoted text clipped - 51 lines]
>> >
>> > Help, help, help
 
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.