 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
MS Access Forum / General 1 / June 2006Data Being Updated by Another User
I keep getting this error: The Microsoft Jet database engine stopped the process because you and another user are attempting to change the same data at the same time. There is no other user. I've tried moving the table to another database, by importing, exporting, and by copy/pasting. I've tried a Make-a-new-table query. I've tried copy/pasting the table within the same database. I can put that table and another together in a select query, as long as I don't specify any criteria, if I do, I get the error. The only thing I can guess that might have caused this is that I put the database on a jump drive and then pulled it out of its socket without doing the Remove Hardware stuff. Is there a way to undo this? Thanks! JA How are you attempting to update the data? What objects are open in your application? > Is there a way to undo this? very hard to say based on what you've posted. it's not cause you didn't remove the hardware. Jet returns that error when more than one process attempts to edit the same record at once. There doesnt have to be two seperate "users". the usual cause for me is a combination of a bound for open while trying to perform a recordset update in code... but anything could be causing this. do you have more details? Rick and Bill, I had 2 tables in a query, and when I would specify criteria to look for, I would get the error - the query wouldn't open. Also, when I tried to copy the table (that was giving the error), either open or closed, I would get the error. I'm not talented enough to do anything in code! :-) But, I just Compacted and Repaired, and now it seems to be ok...... Well, I compacted and repaired, and now it is ok. >> Is there a way to undo this? > [quoted text clipped - 6 lines] > trying to perform a recordset update in code... but anything could be > causing this. do you have more details? > I'm not talented enough to do anything in code! :-) no talent required for vba, actually talent's a drawback (that's always been my excuse!). > But, I just Compacted and Repaired, and now it seems to be ok...... glad that worked.... a little puzzeled - but all's well that ends well :) > > I'm not talented enough to do anything in code! :-) > [quoted text clipped - 5 lines] > glad that worked.... a little puzzeled - but all's well that ends well > :) It's quite possible (likely even) that the message is a lie! I realise this is a little late and I'm jumping in at that end but yesterday I had to deal with precisely this problem. The cause was corruption in a record (it was a Memo field - it's almost always a Memo field ...). The solution was to create a new duplicate table and copy all the rows before the corrupted row and all the rows after the corrupted row into the new table. Then I deleted the old table and renamed the new. NB you have to remove any table links first and re-create them afterwards. Jeff Bailey Sounds like a good reason to put your memo fields in a separate table from the one they're associated with and set up a 1:1 relationship, that way you only have one relationship to delete and you only lose the contents of the memo field affected  SignatureTerry Kreft > > > I'm not talented enough to do anything in code! :-) > > [quoted text clipped - 18 lines] > > Jeff Bailey Terry In the words of the immortal Afferbeck Lauder "eggwetter gree" Pity we can't learn from foresight as effectively as we learn from hindsight! Jeff > Sounds like a good reason to put your memo fields in a separate table from > the one they're associated with and set up a 1:1 relationship, that way you [quoted text clipped - 27 lines] > > > > Jeff Bailey Don't know what you are talking about, this isn't foresight or hindsight. I was saying that it would be better to have the memo fields in a separate table, you could implement this fairly easily unless you have a large number of tables with memo fields. SignatureTerry Kreft > Terry > [quoted text clipped - 36 lines] > > > > > > Jeff Bailey Ah, got the first bit, if you'd said "egg wetter gree", I'd have got it straightaway. I understand your second comment now. SignatureTerry Kreft > Don't know what you are talking about, this isn't foresight or hindsight. > [quoted text clipped - 49 lines] > > > > > > > > Jeff Bailey Off Topic Sorry for the confusing eggwetter bit. I've been a fan of a small book by Afferbeck Lauder, called Fraffly Well Spoken, since about 1970! My current favourite expression is: May kerosene furry pears ... So I'll have to catch the bus! > Ah, got the first bit, if you'd said "egg wetter gree", I'd have got it > straightaway. I understand your second comment now. [quoted text clipped - 63 lines] > > > > > > > > > > Jeff Bailey |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.