I have an Access 97 database that is on a LAN with about 15 different users. The database runs without problems when it is run on just one local computer, but when it is run on the network with multiple users all at the same time, I often get a "Not a valid bookmark" error. This usually occurs in my user log table, which is probably written to and edited more than any other of my tables. This table has user name, user login time, and module as the primary key. It also has a logout time field. The login and logout time fields are date/time fields. This table is written to or edited every time a user enters or exits a form. When the error occurs it means that there are errors in each field of one or more records in that table. If I repair the database it temporarily solves the problem. I think the problem is related to so many people editing or adding to the same table at the same time. It may also have something to do with having the date/time field as part of the primary key. I have my update retry intervals set to 1 sec between retries, 10 retries, and record locking set to edited recording locking. What could be causing this to corrupt my data?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
How did I get a "Not a valid bookmark" error?
- Thread starter Arnold
- Start date
Well... sounds like solving this one is going to be a breakthrough! I don't think I have much help, but some ideas:<br>
<br>
If it runs fine on your PC, and not on someone else's, then check out their user rights/permissions. Are you sure you don't have ANYTHING in a form or table or code or macro pointing to an .html file that you have rights to and some other users don't ? Also if such a file existed, and was then removed from its original place, this error will appear. I would first check this out thoroughly before suspecting something else.<br>
<br>
Our company have 20 users accessing an Access 95 database. I found when tables became greater than about 12000 records, strange locking errors occur, and sometimes funny data appears in it. I found out that Access was not meant to be used with so many users accessing it, and so many records. I think Access 97 and 2000 handles it better, but if you have 95, you can expect some problems with large tables many users and updates. Our answer was eventually SQL Server.<br>
<br>
<br>
A process of elimination should find the problem. Try running the database on another PC, off the network (this will indicate if there is a refereced file on the server). See if the problem occurs only with a few users (when their PC's update the tables). Try importing the table into a new database and see if there are problems. Next import forms, code referencing it etc.<br>
<br>
Good luck!
<br>
If it runs fine on your PC, and not on someone else's, then check out their user rights/permissions. Are you sure you don't have ANYTHING in a form or table or code or macro pointing to an .html file that you have rights to and some other users don't ? Also if such a file existed, and was then removed from its original place, this error will appear. I would first check this out thoroughly before suspecting something else.<br>
<br>
Our company have 20 users accessing an Access 95 database. I found when tables became greater than about 12000 records, strange locking errors occur, and sometimes funny data appears in it. I found out that Access was not meant to be used with so many users accessing it, and so many records. I think Access 97 and 2000 handles it better, but if you have 95, you can expect some problems with large tables many users and updates. Our answer was eventually SQL Server.<br>
<br>
<br>
A process of elimination should find the problem. Try running the database on another PC, off the network (this will indicate if there is a refereced file on the server). See if the problem occurs only with a few users (when their PC's update the tables). Try importing the table into a new database and see if there are problems. Next import forms, code referencing it etc.<br>
<br>
Good luck!
- Thread starter
- #3
dlblake,<br>
Thanks for your response. I am sure that I don't have any .html files in any part of my database, so that shouldn't be the problem. I have tried the program on individual computers and have had no problems with it. I ended up drastically decreasing the number of records that were wrote to my user table and the number that were edited. This seemed to have fixed my problem. I think that the problem just had to do with the number of updates to the table. (I am currently using Access 97.) I had problems in the past with multiple accesses to the same table at the same time. I changed the structure of the database around to eliminate this from happening and it solved the problem. As far as I can tell, Access just can't handle a lot of users hitting the same table at the same time. <br>
<br>
The number of users for our system will continue to grow, so we have started talking about coverting our backend to SQL Server. Do you have any idea how much work would be involved in switching my backend over to SQL Server? Non of my forms have Record Navigation buttons on them. I always access the data by using recordsets. Some of my recordsets are defined globally, but many of them are defined in each procedure. Would I have to add a link to the SQL Server each time I open a record set, or what? What is all involved? A have somewhere between 40 and 50 thousand lines of code.<br>
Thanks for your help.<br>
Thanks for your response. I am sure that I don't have any .html files in any part of my database, so that shouldn't be the problem. I have tried the program on individual computers and have had no problems with it. I ended up drastically decreasing the number of records that were wrote to my user table and the number that were edited. This seemed to have fixed my problem. I think that the problem just had to do with the number of updates to the table. (I am currently using Access 97.) I had problems in the past with multiple accesses to the same table at the same time. I changed the structure of the database around to eliminate this from happening and it solved the problem. As far as I can tell, Access just can't handle a lot of users hitting the same table at the same time. <br>
<br>
The number of users for our system will continue to grow, so we have started talking about coverting our backend to SQL Server. Do you have any idea how much work would be involved in switching my backend over to SQL Server? Non of my forms have Record Navigation buttons on them. I always access the data by using recordsets. Some of my recordsets are defined globally, but many of them are defined in each procedure. Would I have to add a link to the SQL Server each time I open a record set, or what? What is all involved? A have somewhere between 40 and 50 thousand lines of code.<br>
Thanks for your help.<br>
- Status
Similar threads
- Locked
- Question
- Locked
- Question