Reserved error(-1517)

Can somebody explain what this error is?
We have a billing, payroll and reporting application that we distribute to about 250 users with an mde every 2 weeks when changes are made. Last week when we sent our new copy out, about 60 users started getting this problem in their app (possibly more were effected). When we replaced the app with the exact same copy it fixed the problem. Also a repair and compact solves the problem. The error pops up in different places accross the app. I would like more information about the possible causes so that we do not have a repeat of this issue this week when we promote a new version. I'll split points and possibly add some more, for the best suggestions.
LVL 3
iabakerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

walterecookCommented:
while this error is itself a bit cryptic, I believe it most often (if not always) stems from a linked table error.  That would help explain why it pops up intermittantly throughout your app.  You may want to try to isolate it though to see if it is ONE table or many tables.  If it is one there may be something quirky about a field name or something.
What is your BE and how are you connecting to it?

That being the case, I'd run some code on open of the database to refresh the links.
You may also consider checking the validity of the link before certain events, too.

Hope that helps
Walt
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jadedataMS Access Systems CreatorCommented:
Hey! iabaker,

  Negative error numbers are usually generated by another application and passed back to Access for reporting.
  There should be a text explanation coming thru with the error number, and MAYBE, if your lucky the name of the app ACTUALLY raising the error.

  What external applications, OCX controls or such does this distributable play with during a runtime session?

regards
Jack
0
iabakerAuthor Commented:
hey guys,

Jadedata, it actually comes through as an error no 3000. the description says "Reserved error (-1517); their is no description for this error."

I think it is a link problem, walter. we've got some startup code that was recently put in that is changing the type of a field on a few linked tables by creating a new field with the new type, updating the new field with the old field data, deleting the old table and renaming the new. Somehow that seems to be screwing up the link in the app. I can't seem to recreate the error on my machine. I have inserted some code to refresh the links after the type change, its testing it that is the problem. Is there a way to get more information about the link. possibly a way to test to see if it is bad? I can open the table fine manually, but the code won't run on it until the link is refreshed.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

walterecookCommented:
Well,
one direct way to test the link in code is try to open a query based on the linked table.  Or try a dlookup on the table itself:
somevar = dlookup("someField", "theTableName")
if that line bombs, clearly it can't open the table.

Walt
0
jadedataMS Access Systems CreatorCommented:
Add a time-out loop of a few seconds after the changes are made to the tables in the linked file.
It may be that the code engine is over-running Access's ability to refresh the system objects tables before continuing to the code that then tries to use these objects.

Also force the change to the link before you move on to using the objects
currentdb.tabledefs("TableName").connect = currentdb.tabledefs("TableName").connect
(goofy as it may look, it could work....)

It isn't happening on your own machine probably because it knows you'll be very disappointed with it if it screws up.

0
iabakerAuthor Commented:
It was the link that was messed up. Thanks for the help.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.