Share via

Access Reserved Error -1524

Anonymous
2022-06-30T15:15:08+00:00

Colleague started running into this error this morning when users attempt to generate some reports.

No recent changes, underlying query for the report loads fine. Removed many of the objects and controls from the report in an attempt to isolate the problem, but it persists regardless.

Is anyone else experiencing similar? I have not yet checked if there was a recent Office Update that came through, but the last time we experienced something of this nature it was due to a bug in a recent update.

If anyone else began having this issue today, I'd appreciate at least a bump on this thread so those of us dealing with it can proceed accordingly.

Thanks!

Microsoft 365 and Office | Access | For business | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

2 answers

Sort by: Most helpful
  1. Anonymous
    2022-07-14T06:50:47+00:00

    A reserved error is commonly encountered when connecting the Access front-end to an SQL Server. However, some MS Access users reported receiving the ‘reserved error’ when executing a query, running a macro, updating a .mdb split database, and other scenarios.

    Causes of the Access Reserved Error 1524:

    • ODBC driver is not updated in the system
    • The Database record that you’re trying to access using ODBC is corrupted
    • Insufficient Memory
    • Corruption due to oversized database file size

    Solutions:

    1. Update ODBC Driver

    https://support.microsoft.com/en-us/office/administer-odbc-data-sources-b19f856b-5b9b-48c9-8b93-07484bfab5a7 

    1. Use Compact and Repair Method

    https://support.microsoft.com/en-us/office/compact-and-repair-a-database-6ee60f16-aed0-40ac-bf22-85fa9f4005b2 

    1. Import Old Database into New Database

    https://support.microsoft.com/en-us/office/import-or-link-to-data-in-another-access-database-095ab408-89c7-45b3-aac2-58036e45fcf6  

    Best Regards,
    Adi

    Was this answer helpful?

    0 comments No comments
  2. George Hepworth 22,855 Reputation points Volunteer Moderator
    2022-06-30T16:03:14+00:00

    It could be the result of a corrupted record in a table which is queried for the report. See item #38 here.

    Make a back up of the accdb BACK END. Compact and Repair it. See if that resolves the problem for that copy of the BE.

    Was this answer helpful?

    0 comments No comments