top of page

Feedback requested: There is no message for this error

Updated: Mar 13

Nobody likes seeing error messages. But when you do, you want the error message to be clear and to the point.

Unfortunately, very occasionally, you may see an error message similar to that shown above.

The message is both unclear and unhelpful in resolving the problem

In fact, any message like this is a bug and the Access team want to know so they can try and fix it if possible.

If you do see this, please let us know the precise circumstances (including Access version and bitness) where it occurs and we will be happy to report the bug on your behalf. Between you, us and the Access team, we can hopefully eradicate these reserved error messages.

NOTE: The reserved error number may vary but always appears to be less than zero.

Please include the reserved error number as part of your feedback.

In the past few weeks, we have passed on details of four of these errors:

1. If an MDB file contains a table with a corrupted record, trying to save as ACCDB triggers reserved error -1517 as shown below

2. Relinking a SQL table containing a Spatial Index triggers reserved error -7747:

3. Repairing a database after receiving a 2501 error when using SendObject to email a PDF triggered reserved error -3034. In this case, error handling was in use and the standard Access error 3000 is also shown in the error message:

For info, there are two standard Access errors (2626 & 3000) to handle these reserved errors:

4. Trying to save a query that contains a reserved word (e.g. Language) in SQL view, causes Reserved error -1001 and the field affected is highlighted

Despite this the query can be opened in design view and run without error.

The error is easily fixed by enclosing the field name(s) containing reserved words in square brackets e.g. [Language].

However, a clear error message would be far more helpful. Something like this:

Language is a reserved word in Access – either enclose the field name in square brackets or rename the field

Other reserved errors reported in forums or online sites include:

a) Reserved error (-2037): Linking tables in A2016 - MS Access 2016, Reserved error (-2037); there is no - Microsoft Community

b) Reserved error (-1517): query linked ODBC record with corrupt data How to Resolve "Reserved error" in Access (

c) Reserved error (-1104): navigating a database - ms access reserved error (-1104) there is no message for this error (

NOTE: Some of these messages go back several years.

We believe there are other similar errors lurking out there. Many (but not all) appear to be associated with corruption and/or linked tables.

Please pass on sufficient details so that the Access team can reproduce / hopefully fix the error.

Thanks in advance for your feedback!


I am pleased to report that we have already had a response from the Access team outlining the meaning of these errors. The importance of having an example database for MS to reproduce these errors was again stressed

209 views2 comments

Recent Posts

See All
bottom of page