Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Microsoft Jet Database Engine Stopped Process

Status
Not open for further replies.

amwmsh

IS-IT--Management
Jan 8, 2003
40
US
I have a database that resides on a company shared drive. Also on this shared drive are some spreadsheets. These spreadsheets use Microsoft Query to pull information from the database. For a while we were getting some ODBC error messages concerning drivers but have since fixed that problem. Now a new problem has showed up. I have been visiting each user (approximately 40 of them) to make sure they have the necessary ODBC drivers loaded.

While opening the spreadsheet one individual gets the following error message:

Microsoft Jet Database Engine has stopped the process because you and another user are trying to access the same data at the same time.

This is the only user receiving this particular error message. I can immediately walk to the next machine and open the database and spreadsheets with no problem but as soon as I return to the non-working user I get the same error message.

Any thoughts on how I can remedy this?

Thanks,
Amanda
 
Close Access. Delete the related ldb file from user's system and try again. I don't particularly care about apathy
 
I searched for any ldb files on the users system in order to delete them and found none. Still trying to see what I can do. If anyone has any more advice it is greatly appreciated.

I was going to try and compact and repair the database at the users machine (the database resides on the server) but everyone else in the organization is successfully pulling up these files and I am scared if I do the compact/repair it will cause new problems since everyone else is fine.

Thanks,
Amanda
 
This is from Microsoft article Q279334. This may help.

How to Determine What Users/Workstations Are Causing the File to Be Marked Suspect

You can determine which workstation and user caused Jet to mark a .mdb file as suspect with the LDBView utility, which is available by downloading Jetutils.exe from the following Microsoft Web site:

For additional information about the Microsoft Jet Utilities, click the article number below to view the article in the Microsoft Knowledge Base:
176670 ACC: Microsoft Jet Utilities Available in Download Center

Ldbview let you observe which users are currently logged into the database, as well as any users that may have left the file in a suspect state.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top