Access not opening

[Glenley]

I recently got a new laptop and when i try to open my DB file, at random times it will create the .laccdb file but not actually open. This renders my DB file inoperable because access sees it as being open but the program never actually opens when this happens. Luckily, i create several backup copies any time I update my DB but this is a problem. Anyone else had this happen? Or know how to fix this problem? I always compile my DB files before distribution.



Thanks

[Micron]

I'd say it must be open or else the lock file would not be created. Take a look in Task Manager (perhaps ctl+shift+esc for you) and see if you have more than one listing for that db. Perhaps there is a conflict.

[Welshgasman]

Did you change bitness in your app when installing on the new computer?

[Glenley]

Task manager doesn’t show it as being open

[Glenley]

I’m not even sure how I could do that. Where do you check that?

[CJ_London]

Try opening with the shift key down to bypass any opening code. Just wondering if you have startup code causing an issue

also what version of access were you using previously and what are you using now

I’m not even sure how I could do that. Where do you check that?

same place - in access file tab. Depends on you current version, might be under help or account

[Micron]

Task manager doesn’t show it as being open

Forgot to mention that it could appear in the list of background processes and not Apps. I have a similar issue with Outlook. When it fails to launch it is always listed in processes. When I delete it, Outlook then opens.

[Glenley]

I'm running MS 365, same as my old laptop and I don't see it in my background processes. I have an autoexec macro running at startup, I'll try bypassing that. The issue with that is the problem only happens at random times so I won't know for sure if that's solving the problem. I'll give it a shot though

[Welshgasman]

If it is at random times, then perhaps it is a data issue?

[Glenley]

I tend to think it's either an Access or Windows issue because the opening process stops as soon as the .laccdb file is created. It's quitting before the data is accessed. For some background, I'm working with tables linked to SharePoint

[Micron]

It may be doing an abnormal termination, leaving the lock file in place - as if you pulled the pc plug.

[Glenley]

Micron, do you have any ideas on what could cause that? I’ve considered re-installing Access but I’d really like to understand what’s causing it

[Welshgasman]

Have you looked in the Event Manager for any clues?

[Micron]

Micron, do you have any ideas on what could cause that? I’ve considered re-installing Access but I’d really like to understand what’s causing it

Sorry, no. Since I'm a 365 subscriber, the first time it happened I got on line support. They did an install of 64 bit office. Whoops, says I. I don't want 64, I want 32. Did another removal and install. Problem gone until next time. That's when I found Outlook in processes and not apps where it should be. So the point is, the re-install didn't solve that so I wouldn't put a lot of faith in it if you're planning that as a solution. You haven't said you have the same condition though?

[Glenley]

Micron, it happened again today and you were right. I found it in the background processes in task manager. Manually ended the task which allowed me to delete the .laccdb file and was able to re-open the file. Did you ever figure out what was causing it?