 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
MS Access Forum / Multiuser / Networking / March 2005Locking Record File Problem?
Hello, I am having a problem with a multiuser server based Access 2000 database and would really like some help understanding what's going wrong, why and what the options are to sort the problem. Backend and mdw file are on a shared network server. Frontend is on each user's pc. Backend and mdw have different filenames, no record locking strategy is in use and there would typically be a maximum of 6 concurrent users. User's pc's have a mixture of Office 2000, Office 2003 on Windows 98, Windows 2000 or Windows XP. The db has been in use for some weeks without any problems then we started experiencing frequent instances where users could not open the database; the error message is "Unrecognized database format drive:\path\filename.mdb". This message never occurs when the first user opens the database - it only seems to appear when further users attempt to open it - but it's not guaranteed to happen every time more than one user opens the database - it appears random as to whether it will or won't happen!! The only solution to date has been to take everyone out of the database then compact and repair which always fixes the problem until next time it happens - currently around 3 times a day. Is this a record locking conflict issue or is the record locking file or database simply becoming corrupted because of communication problems between user pc's and server? Can anyone give me a checklist to go through that may help me eliminate the obvious and pin the source of the problem down? TIA One possibility to check is that one of your users does not have full privileges (read-write-create-delete) to the directory containing the BE database. If that user happens to log on first, the .ldb file will be created on their local hard drive which will prevent an other user from accessing the database. A second possibility a little harder to find is one of the PCs network interface card is failing intermittently. If you have a server administrator, he/she can check for this. TomU > Hello, > [quoted text clipped - 23 lines] > > TIA >I am having a problem with a multiuser server based Access 2000 database and >would really like some help understanding what's going wrong, why and what [quoted text clipped - 14 lines] >database then compact and repair which always fixes the problem until next >time it happens - currently around 3 times a day. What is confusing is that if someone is using the database they don't get kicked out or get an error message. It's only when a user starts up an app which accesses the Access database that they get the message. Someone already in it can happily work all day long and likely not even notice a problem. >Is this a record locking conflict issue or is the record locking file or >database simply becoming corrupted because of communication problems between >user pc's and server? Can anyone give me a checklist to go through that may >help me eliminate the obvious and pin the source of the problem down? This is definitely a corruption issue of some sort. Nothing to do with record locking. For more information on corruption including possible causes, determining the offending PC, retrieving your data, links, official MS KB articles and a list of vendors who state they can fix corruption see the Microsoft Access Corruption FAQ at http://www.granite.ab.ca/access/corruptmdbs.htm Tony -- Tony Toews, Microsoft Access MVP Please respond only in the newsgroups so that others can read the entire thread of messages. Microsoft Access Links, Hints, Tips & Accounting Systems at http://www.granite.ab.ca/accsmstr.htm Thanks Tony, A link on your website directed me to useful Microsoft article (285822) that explains how to use Microsoft Jet Roster to determine who is logged on to a database and whether or not the user connection was terminated under normal circumstances. I have installed the code and am able to see who is logged in - the Immediate window also returns a value under a column headed "SUSPECT_STATE". I assume that "Null" means the user connection is normal and that "1" means the user connection has terminated abnormally - is this correct or does "1" have a more specific meaning? I hoped that by using this code I would be able to identify a single user who's connection was repeatedly terminating abnormally (faulty network card, cabling etc?) and solve the problem quickly but instead I have found that a number of different users connections are terminating abnormally (long after they have logged on to the database without a problem)- it seems unlikely that they have all developed hardware faults at the same time! I have checked that all database users have full access permissions to the folder containing the back end database and am unsure what direction I should be looking in next? Any advice gratefully received. TIA > >I am having a problem with a multiuser server based Access 2000 database and > >would really like some help understanding what's going wrong, why and what [quoted text clipped - 42 lines] > Microsoft Access Links, Hints, Tips & Accounting Systems at > http://www.granite.ab.ca/accsmstr.htm |
Reply to this Message |
 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.