Application or Database Crash

Tophan

Registered User.
Local time
Yesterday, 23:20
Joined
Mar 27, 2011
Messages
420
Good morning. I was working on a database yesterday and had just set the Display Form in the options of the Database. I closed the database and when I tried to reopen it, it seemed to have crashed. Luckily it automatically created a backup of what I was working on but right now, the .laccdb file is still showing in file explorer and when I tried to open the access application, it prompted me to open it in safe mode and again prompted me to save a backup of the same database.

I had started this thread in the Queries forum as I was getting help on another issue when the crash happened. I was just asked to try uploading the crashed DB so I have attached it. I hope it doesn't cause issues for anyone. Also attaching a screenshot of File Explorer. The .laccdb file has been there since the crash.

1769526195292.png
 

Attachments

The lock file still exists as the file is open in the background.
Open Task Manager, go to Background Processes, select Microsoft Access then End Task.

You should now be able to delete the lock file in File Explorer.

Next I recommend you decompile your app to remove any corrupt compilation code. For instructions, see my article
 
I get no errors or crashes when I open the file. A form DOES open when I open the DB. I also don't see a "crash report" internally. When Access crashes, it sometimes leaves behind a table called "Recovery Objects" or something like that. If you got a separate copy of the file you loaded, check that file for a table you didn't create with the name "Recovery" in it. See if there is a message there.
 
I'm not seeing
The lock file still exists as the file is open in the background.
Open Task Manager, go to Background Processes, select Microsoft Access then End Task.

You should now be able to delete the lock file in File Explorer.

Next I recommend you decompile your app to remove any corrupt compilation code. For instructions, see my article
Hi,

I don't see Microsoft Access listed in the Background Processes

1769528162012.png
 
I get no errors or crashes when I open the file. A form DOES open when I open the DB. I also don't see a "crash report" internally. When Access crashes, it sometimes leaves behind a table called "Recovery Objects" or something like that. If you got a separate copy of the file you loaded, check that file for a table you didn't create with the name "Recovery" in it. See if there is a message there.
Hi. I'm not seeing a recovery objects file/table either.
 
Good morning. I was working on a database yesterday and had just set the Display Form in the options of the Database. I closed the database and when I tried to reopen it, it seemed to have crashed. Luckily it automatically created a backup of what I was working on but right now, the .laccdb file is still showing in file explorer and when I tried to open the access application, it prompted me to open it in safe mode and again prompted me to save a backup of the same database.

I had started this thread in the Queries forum as I was getting help on another issue when the crash happened. I was just asked to try uploading the crashed DB so I have attached it. I hope it doesn't cause issues for anyone. Also attaching a screenshot of File Explorer. The .laccdb file has been there since the crash.

View attachment 122959
Database opens fine with no errors.
 
Try to delete the lock file. If you can't, look for MSACCESS.EXE in your process list. End that task and try again.
 
Try to delete the lock file. If you can't, look for MSACCESS.EXE in your process list. End that task and try again.
I was able to delete the locked file but MSACCESS.EXE is not listed in the Task Manager Process List
 
Should I just delete the original database? I tried opening it after deleting the locked file but it still won't open for me.
 
One more thing. I just restarted my laptop and tried to open Access and got the below prompt. This only happens after a restart of the computer.

1769529651498.png
 
The safe mode screen occurs when Access has failed to open on the previous two occasions in succession e.g because you tried to open an app where the lock file existed and prevented the app opening.
 
As noted in your earlier thread, I am unable to reproduce the behaviour you are experiencing.

More fundamentally, however, I think your model needs amending as below to avoid the current encoding of data as column headings in tblProjects:

DrawingRegisterModel.gif


PS: I've just noticed the redundant DrawingID column in tblDwgTypes. This can be dropped.
 
Last edited:
Ok - So I need to breakup the tblProjects table and link the consultants to the projects with a separate consultant and consultant type table. I'll do that.

Any other issues? Always willing to receive feedback from this forum.

Thanks.
 
Any other issues? Always willing to receive feedback from this forum.

I'm a little unsure about the relationship type between tblDwgReg and tblDwgTypes. At present its many to many, modelled by tblDwgRegDetails. This is predicated on the drawing type being an attribute of the relationship type, i.e. revisions of the same drawing can be of different types, rather than each drawing always being of one type, regardless of the revisions.
 
That is correct - the same drawing can be different types depending on the phase of the project. So for example, at the early stage, the architect may prepare a site plan for client and statutory approval so that drawing type would be "A". Next that same site plan would be part of the contract package so it would have the "C" for contract. The site plan, just before constructions starts, would then be a preliminary drawing. Once the ground is cleared and actual conditions on site are confirmed, the site plan now becomes a for construction drawing. At the end of the project, the architect will then prepare as-built drawings to handover to the client for their records. Each type of drawing can be revised several times until all details are confirmed or agreed.
 
I am a bit reluctant to mention this because it doesn't always lead to anything useful. However, if you have a good idea as to when your DB crashed (and if you still have the backup, check its creation date as a hint), you can open the Windows Event Viewer. Entries therein are sorted by date/time so you should be able to find if there were any system events logged at that time. The Application logs MIGHT (rarely) have something useful, too.

If so, you might be able to find an error or status code that would be written in hexadecimal and it might look like 0x800hhhhh (the h's being hexadecimal digits). Or 0xC00hhhhh, since this was an ugly crash. The crashing process would be Access - probably MSACCESS.EXE - and there MIGHT be a secondary named module if the crash was in one of the VBA >> Tools >> References libraries.

As I said, this doesn't always lead to something useful, because it is a crap-shoot as to whether the system event log would get an entry for an Office event. But I've seen it before, so there is a chance. Knowing the error code and faulting module would be helpful.
 

Users who are viewing this thread

Back
Top Bottom