Bookmark Error

I have encountered error 3159 - Not a valid bookmark. The strange thing is that it occurred while executing the following statement. "Set db=CurrentDb"

I don't get it, where is the reference to a bookmark?
LVL 5
gbentleyAsked:
Who is Participating?
 
TrygveConnect With a Mentor Commented:
OK, you got it.
0
 
TrygveCommented:
First: Be sure that db has not been dimension as a bookmark. Yes, it sounds stupid, but we all do things like this and its "impossible" to see it by reading your own code.

If everything is correct, try this; While in design mode in a module, select Debug, Compile and Save All Modules. If you get any errors they should be able to guide you to the problem. If not enter Tools, References and see if any of the marked lines have the word missing in the description. If so, remember the file names,  deselect these items and then reenter them by browsing your way to them.

Still problems. Try compacting and repairing the database. Still problems. Make a new database and import all the object into it. Still problems; Reinstall Access/Office.
0
 
gbentleyAuthor Commented:
OK, the code is not the problem. This is an error that occurred in a database that has been used for some time. Repairing did fix the problem.

My question is intended to find out what could of caused this to happen. There is an intermittent error in another place int this database and I am trying to track EXACTLY what is going on.

I am a programmer from the old school which says that reinstalling does not "solve" the problem because it doesn't explain why it happened and how to stop it in the future.

If no-one has a better answer, I will get you to re-post and give you the points.

Thanks
0
Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

 
TrygveCommented:
I think that this is one of those "problem with no reasonable reason" problems. I also like to know what happens all the time, but some problems will keep you searching for hours and hours and you end up finding nothing.

From time to time modules and other objects "get stuck" in the database. For example. Deleting a module and import the same module from another base may cause a message of duplicate occurences of procedures etc. I think the reason for this is that Access does not actually remove objects that is deleted. They keep stuck till the next compact/repair session. Most of the time this does not cause you any trouble except the fact that your database keep growing.
0
 
gbentleyAuthor Commented:
Thanks for that. I'm having a lot of trouble with unreliable connections and queries. The process that Access goes through is:

Drop the SQL connection if it exists
Connect to a SQL table
Run a query on that table and some local tables
Drop the connection
Export some data to SQL
Call a SQL stored procedure
Then do it all again on another SQL database/table, and again, and again, and.......

Note that all the attached tables have the same name so it is drop GLChart, reconnect to a different GLChart, query it, etc.

What I need is to get this routine to the stage where it works EVERY time the user clicks the button. They have just moved from a legacy system and this is the expected reliability. I have enough trouble explaining WHY you have to restart SQL/NT Server to fix errors. That didn't happen on the old system! It doesn't help that I don't know WHY this is the case. It is surely possible to write an operating system that doesn't leak memory?

Any further suggestions as to how to trap this kind of thing or how to recover from the errors in a polite fashion would be greatly appreciated.

0
 
TrygveCommented:
Would it be possible for you to have all the tables attached, with different names ? This would prevent your application from leaking memory due to your creation/deletion of connections etc. As for your errors, you should be able to deal with almost any error by error trapping, but this will of course demand lots of checking to make bullet proof.
0
 
gbentleyAuthor Commented:
It is virtually impossible to set up the connections as permanent. This is because the specific SQL database that it links to is dependant on user selections. The number of DBs can also grow with time.

I have found that there are SQL problems tied up with this error so I don't think it is purely an Access issue.

I would like to close this question and then create another worth 100 points to award Trygve.

Trygve, please answer the next question with this name.
0
 
gbentleyAuthor Commented:
OK, I won't delete it.

Trygve, please answer and I will award the points to you.

0
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.

All Courses

From novice to tech pro — start learning today.