Reserved error -1517

  • Thread starter Thread starter George Lob
  • Start date Start date
G

George Lob

I just started getting this error and was wondering if anyone has
encountered it. The error is happening during an append query to a table. I
have been running this query for quite a while with no problem, so I know
that the query is OK.

Any help would be appreciated.

Thanks,
George
 
First, what conceivable relevance does your question have, to Exchange 2000?
None. So maybe do not post it to their newsgroups! (Just as we would not
like to start getting Exchange 2000 questions here.)

Is the table a linked table? Have you changed its structure recently? If so,
try deleting & recreating the link.

HTH,
TC
 
George Lob said:
I just started getting this error and was wondering if anyone has
encountered it. The error is happening during an append query to a table. I
have been running this query for quite a while with no problem, so I know
that the query is OK.
Click to expand...

TC is correct. Deleting and recreating the table links will fix the
problem as will compacting the BE and the FE.

I've noticed this problem several times when I've added a foreign key
to a table in the backend which was inserted into the middle of a
table. Everything would work fine for days or weeks until the backend
was compacted. Then the FE would puke with the -1517 error you
mentioned whenever that particular table was accessed. But deleting
the link and recreating the link made it work again.

http://www.granite.ab.ca/access/reservederror1517.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
Thank you both for the answer. TC, I posted my apologies to the exchange
groups as soon as I saw my mistake, which was right after my original post!
Everyone makes a mistake once in a while.
 
It occurs for me when the Appened table has had a filed
name change. Relink the table and you should be ok.
 
Tony Toews said:
TC is correct. Deleting and recreating the table links will fix the
problem as will compacting the BE and the FE.

I've noticed this problem several times when I've added a foreign key
to a table in the backend which was inserted into the middle of a
table. Everything would work fine for days or weeks until the backend
was compacted. Then the FE would puke with the -1517 error you
mentioned whenever that particular table was accessed. But deleting
the link and recreating the link made it work again.
Click to expand...


Hi Tony

I remember getting a reproducable reserved error (I can't remember
which one) after I added a field to a back-end table through code. I
eventually found a reference to the error code. The description was
something like "Invalid column number". This prompted me to refresh
the link, which fixed the problem. In my case, compacting did not fix
the problem (from memory), so it was unclear what was going on. Now I
always refresh the link if I have change the back-end table structure
through code; not that I do that often, anyway!

Cheers,
TC
 
Back
Top