Feb 03 2022 02:22 PM
Feb 03 2022 02:22 PM
Error 3048 started one day, after NO CODE CHANGES for several months!
Someone suggested to look at all .OpenRecordSets and verify that there is a "Close" for each "Open".
I have done so, and the problem persists.
I start the application and only 15-20 OpenRecordSet runs go by before the error occurs.
Is there a way to look at Access TableIDs along the way to help figure out what is going on?
Feb 03 2022 02:26 PM
Feb 03 2022 03:09 PM
Feb 04 2022 05:58 AM - edited Feb 04 2022 06:17 AM
This same error started for me today too, after a MS Office update applied to my laptop. I have just one MS Access DB open with a split-end. It manages to load, but can't do anything without this error popping up. The project is decades old, and I've keep very precise in closing recordsets and then setting them to null once done with them.
Microsoft have updated something, and screwed up part of MS Access.
The thread linked by Karl Donaubauer had solutions to this problem that worked for me; MS update has caused the issue. Read that thread for updates/fixes/commentary.
Feb 04 2022 02:37 PM
I am having the same error. It is clearly from the latest Access update. I have a machine running the old version that has not yet updated and this error does not happen. We need clear instructions from Access if this is being fixed or what steps we have to take to work around this problem.
Feb 04 2022 02:53 PM - edited Feb 04 2022 03:44 PM
If you are the Todd Haugen I met in Redmond some years ago, then I have to reply directly: ;)
Yes, the Access team has announced a fix. Until then the workaround to put the database in a trusted location is recommended: https://support.microsoft.com/en-us/topic/b2dce32b-b8b0-41f1-ba40-7876e524d9da
Feb 05 2022 10:06 PM
Feb 06 2022 10:59 AM
@Karl Donaubaueryes, same Todd Haugen. Sadly I am no longer with Access, it was my passion but Microsoft had different ideas for me... Hope all is well with you!
Feb 06 2022 04:04 PM
I have the same problem. My ACCDB works fine on other versions of Office and only had this error less than a week ago.
Microsoft is updating something and causing the error...
Feb 06 2022 04:16 PM
Feb 07 2022 08:25 AM
I had a similar problem with a fairly large application in MS Access. I am running Office 2016 and suddenly I started to get the 3048 error after the last update. I had not made any changes to the program. I am anxiously awaiting for an update and fix from Microsoft while my business languishes.
Feb 07 2022 12:04 PM
Feb 08 2022 07:56 AM
Feb 09 2022 12:33 PM
Placing Access file into trusted location fixed the issue for us.
Feb 11 2022 09:38 AM