Share via

Access 2010 : random display of Reserved error (-1104)

Anonymous
2015-06-18T14:48:14+00:00

Hi all,

I am running an Access 2010 frontend linked to a SQLserver 2000.

It has been running for over 5 years without problems but, the two weeks I get at random the Reserved Error (-1104) when working in the front-end.

After this error message, I am unable to save anything and have to stop Access.

I looked everywhere online, but could not find anything on the -1104 error.

The only temporary solution is making a copy of the .mdb file and start using that.

Within a working day the error returns.

The Access file has about 50 linked tables. And over 250 queries, so copy and pasting the queries to a new file is a last option that I hope to avoid.

OS is Windows server 2008 R2.

Any idea what causes this error?  

Thanks in advance,

Jan-Gert

Microsoft 365 and Office | Access | For home | 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

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2015-06-19T05:35:49+00:00

    Is there somewhere a list available with these negatively numbered error code?

    Or are all negative codes reserved without description?

    If there are descriptions for these errors, they are known only internally within Microsoft.  These are errors the user is never supposed to see.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2015-06-18T17:11:33+00:00

    I can't say what's causing it, but pursuing the idea that it may be caused by corruption in the front-end, I suggest you try these steps to remove corruption, if you haven't already:

    1. Compact and repair the front-end.
    2. If that doesn't work, create a new, blank database, and import all objects from the original front-end into the new database.  (You don't have to copy and paste things one at a time; use the External Data -> Import function).  Set any other database properties, such as Startup options, that may be specific to the original front-end.  Then swap the new database in for the original front-end and use it for a while to to see if the problem has gone away.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2015-06-18T19:18:43+00:00

    Hi Dirk,

    Thanks for your reply.

    The compact and repair I already tried to no avail, but your 2nd option could a good idea.

    I will post the result.

    Is there somewhere a list available with these negatively numbered error code?

    Or are all negative codes reserved without description?

    Thanks again!

    Jan-Gert

    Was this answer helpful?

    0 comments