Everyone was out of the database, and the message saying I couldn't perform compact and repair gave my station number as the station that was still in the database! I am allowed to create and delete files in the folder the backend and.laacdb are stored in. If I try to delete the.laccdb I get the message: 'Cannot delete.: It is being used by another person or program. Close any programs that might be using the file and try again.' I've never had this problem in the past year and a half I've been using Access. What version of Access are you using? ---- Look in the task manager for on the Processes tab for an instance of MSACCESS.EXE, if there is, then kill it ('End Process'). Microsoft Access 2013 databases have a file extension of ACCDB. When you open a database file, Access creates a locking file with the LACCDB extension. The purpose of this file is to prevent multiple database users from updating the same record at the same time. Access 2000, XP, and 2003 Compact and Repair Database Open the database in Microsoft Access, click on the 'Tools' menu and select 'Database Utilities -> Compact and Repair Database'. Access 2007 Compact and Repair Database Open the database in Microsoft Access, click on the 'Office Button' in the top left corner then select 'Manage -> Compact and Repair Database'. The trick is to figure out what caused the 'ghost' instance of MSACCESS.EXE in the list of Processes. Back in the day, there was a bug related to implicit comparison to a control in an If. Then construct. If someChkBoxContol Then 'Do SomethingEnd If The solution was easy. Just explicitly compare the control. If someChkBoxContol = True Then 'Do SomethingEnd If (edit: doh! With the mention of.laccdb you must be useing A2007 / A2010. So that issue should not be present any longer, but since it was a bug at one time, I explicitly compare in my If.Thens as a general practice.) Brent Spaulding| Access MVP. Economic reasons for catalytic cracking of alkanes and alkenes. I've rebooted several times, same problem. I haven't spoken with our network admins, but the message I'm getting from Access indicates its my station that is still in the file. Since you've tried all the usual things with no cure, you might try this: Copy the file to a local folder and compact it. You might be able to over-write the existing file with the new compacted one. If not, do the last ditch effort of importing everything into a new database and retire the old one. Bill Mosca http://tech.groups.yahoo.com/group/MS_Access_Professionals. Good idea Bill! I completely overlooked the obvious. Daniel Pineault, 2010 Microsoft MVP MS Access Tips and Code Samples: Thanks, Daniel. I'm sure I've picked up at least as many ideas from you as you from me. ![]() I had to deal with rogue locking files for years with a shared Access 2.0 database. They drove me crazy. Finally, one of the netowrk guys in our department put a file killer app on my computer. When I ran into a hung LDB I just killed it. Sloppy but effective. Eventually, I lost that power due to security tightening so I had to come up with a better method until I could convert the database to a properly split one. Bill Mosca http://tech.groups.yahoo.com/group/MS_Access_Professionals. Definately a good suggestion from Daniel. Also, I would suggest that you use the utility named Who's Connected to find our for sure the computer that is holding the file. I have added the utility to my SkyDrive public folder (, or you are a member of UtterAccess, you can d/l the utility there by The utility will let you know what computer (and the logged in user if you have permission to see that info) is connected to that db in question. I would be interested in the result when you have your computer shut down. ![]() Brent Spaulding| Access MVP. Sorry to be late on this, but I wanted to post my help in case this happens again. This has occurred to me several times throughout our network before. Solution: 1st. Reboot Computer. While it's rebooting Disconnect your Ethernet Cable or turn off your Wi-Fi. That will 'Force' your connection to be lost completely thus removing the locking file. This has been the best and most consistent solution when we come across that. Other option is Utilize SQL Server Management Studio to House all your Table as Back End and you wont have issues like that (combining Access with SQL Server makes for some pretty cool applications). Access for Office 365 Access 2019 Access 2016 Access 2013 Access 2010 Access 2007 Database files can grow quickly as you use them, sometimes impeding performance. They can also occasionally become corrupt or damaged. You can use the Compact and Repair Database command to prevent or fix these problems. The compact process does not compress your data — it makes your database file smaller by eliminating unused space. The Compact and Repair Database command can also help improve performance of your database.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |