Author |
Topic  |
Roger Fredriksson
Average Member
  
Sweden
556 Posts |
Posted - 12 June 2006 : 19:35:42
|
After downloading an Access db to my local stand alone computer Access gives me an error "Microsoft Jet Database engine interrupted your update because someone else is updating the database." (my translation from Swedish) when I try to open it. What could have gone wrong?( I have done it many times before without trouble) and what are my options? |
rf/www.avgifter.com |
Edited by - Roger Fredriksson on 13 June 2006 04:19:36 |
|
ruirib
Snitz Forums Admin
    
Portugal
26364 Posts |
|
Doug G
Support Moderator
    
USA
6493 Posts |
Posted - 12 June 2006 : 22:36:34
|
Also, it seems to me this problem could show up with certain versions of mdb and ado, where updates put a newer ADO version on a computer with an older (Access 97) mdb file. I had a client with this kind of problem once, and there was no easy fix, we ended up restoring a backup copy and updating.
If I run across the details I'll post a follow-up, I do recall there was a MS KB article that popped right up with a google search on the exact english error message.
|
====== Doug G ====== Computer history and help at www.dougscode.com |
 |
|
Roger Fredriksson
Average Member
  
Sweden
556 Posts |
Posted - 13 June 2006 : 05:04:37
|
ruirib, no ldb-file on server or local PC. The db works OK on my server and produces expected response. Doug, I believe that the error message is "The Microsoft Jet database engine stopped the process because you and another user are attempting to change the same data at the same time" and has error number 3191. IŽll work on it later today or tomorrow and will be back telling you what happens but any piece of advice is very valuable because my skills in the area of db, coding etc. is very limited.
|
rf/www.avgifter.com |
 |
|
Roger Fredriksson
Average Member
  
Sweden
556 Posts |
Posted - 13 June 2006 : 08:08:27
|
No need to spend more time on this subject because I only lost about 10 posts compared to my backup (puh!)and since the db is working on the server it easy to get the missing data. After putting them into my backup I just upload the updated backup. However I am going to ask my host Interland if they can explain what has happened. (Pros would probably solve the issue by using http://support.microsoft.com/kb/209137/EN-US/ ) Thank you for your comments. |
rf/www.avgifter.com |
 |
|
ruirib
Snitz Forums Admin
    
Portugal
26364 Posts |
|
Roger Fredriksson
Average Member
  
Sweden
556 Posts |
Posted - 13 June 2006 : 11:10:16
|
IŽll never do that again! The answer from my host was quote: This error typically occurs when a long value column (an OLE or MEMO data-type) has bad data stored in it. Long value columns are typically stored in a separate page from the page that the row is stored in. If a long value column is present in the table schema, the Jet database engine will attempt to read the long value page when reading the row of data. In order to read the long value page, there is a pointer in the row of data. This error is generated when the Jet database engine cannot properly read the long value page from the pointer present in the data row. When viewing a row that exhibits this behavior in Microsoft Access data-windows, the user will typically see the number sign (#) for the entire row.
and they advice me to upload my backup. My db do contain pm-fields so I should perhaps reorganize it to avoid that causing the pb. |
rf/www.avgifter.com |
 |
|
ruirib
Snitz Forums Admin
    
Portugal
26364 Posts |
Posted - 13 June 2006 : 13:31:18
|
Have you tried a Db compact and repair, I suppose? If you have, that probably means that you will need to resort to the backup DB, indeed. If you haven't you may try that, but in situations such as these I have found that it doesn't fix the problem, most of the times.
Do stop the forum whenever you want to download the DB. It's the best thing to do to avoid these situations. |
Snitz 3.4 Readme | Like the support? Support Snitz too |
 |
|
Roger Fredriksson
Average Member
  
Sweden
556 Posts |
Posted - 13 June 2006 : 14:05:30
|
Yes, I did try to compact and repair but got the same error. IŽll stop the forum next time !
|
rf/www.avgifter.com |
 |
|
Roger Fredriksson
Average Member
  
Sweden
556 Posts |
Posted - 15 June 2006 : 13:03:18
|
I did a last download before updating my backup and suddenly it was possible to open the db. I have (of course) no idea why it works. I downloaded it in another folder but that could hardly explain it, or ....? An other thing is that the db worked on the server and adding new posts perhaps made it possible for Access to close the db correctly. I could not find any #-signs - see post above - in new posts nor anything else strange about the content in new posts.
From this very panic-creating situation I have learned: - try to compress and repair
- delete ldb-file
- shut down the forum before downloading db
- make backups more often
- rename corrupt db instead of deleting or overwriting
- add posts to working db on server
- try one more time (in an other folder!?)
This is obvious for many of you but could be of some help for other newbies  |
rf/www.avgifter.com |
Edited by - Roger Fredriksson on 15 June 2006 13:08:36 |
 |
|
AnonJr
Moderator
    
United States
5768 Posts |
Posted - 15 June 2006 : 13:13:41
|
quote: Originally posted by Roger Fredriksson
Amazing how that one never really hits home until its a little past too late. (Yes, this is the voice of experience talking - I've done it too.) |
 |
|
ruirib
Snitz Forums Admin
    
Portugal
26364 Posts |
Posted - 15 June 2006 : 17:58:24
|
You should not be surprised that downloading the server DB again worked. Only the downloaded copy has problems, since you downloaded it while it was being written. The copy in the server was not affected by that, since any operations that were taking place when you were downloading the DB could be completed in the server copy. Does this make sense? |
Snitz 3.4 Readme | Like the support? Support Snitz too |
 |
|
Roger Fredriksson
Average Member
  
Sweden
556 Posts |
Posted - 16 June 2006 : 04:26:53
|
ruirib, I did download it a couple of times - after shutting the forum down - before starting this topic with the same bad result. I do not recall if new posts were added at that time - adding a new post to the db, couldn'tŽt that be the explanation to why it worked again if the server db was corrupted by "bad data" as the reply from support indicate. On the other hand the "bad data" should be present in the db and it is not. Anyhow I know for sure that following the advice from my host-support - update backup-db and upload it - was not the best advice in this case. |
rf/www.avgifter.com |
 |
|
ruirib
Snitz Forums Admin
    
Portugal
26364 Posts |
|
Roger Fredriksson
Average Member
  
Sweden
556 Posts |
Posted - 16 June 2006 : 05:45:48
|
ruirib, your explanation and advice makes sense (as it always does :))and is definitely my # 1 (for what that is worth). As a novice it's however interesting to notice that my hosts support says nothing about that explanation. Am I really the only one in history foolish enough to download without shutting down the forum first?
Even if my list above is rudimentary it do not make any damage to the db to take that measures- it is just a way to exclude possible pbs. |
rf/www.avgifter.com |
 |
|
ruirib
Snitz Forums Admin
    
Portugal
26364 Posts |
Posted - 16 June 2006 : 05:56:46
|
Roger,
I can't assure you that's the cause. I know I've had similar problems before, in those circunstances. It doesn't happen all the time, when you download the database. Most times it won't occur, but as it is possible that it will occur, I recommend shutting down the forum. I have downloaded my share of DBs without shutting down the site / forum, and it is precisely that experience that allows me to give you this advice.
|
Snitz 3.4 Readme | Like the support? Support Snitz too |
 |
|
Topic  |
|