Link to home
Start Free TrialLog in
Avatar of wintactics
wintacticsFlag for United States of America

asked on

Access 2003 Error - Could not update; Currently locked by another session on this machine

Have been developing an Access 2003 appl for a client.  While Access 2003 has been exhibiting some VERY bizarre behavior during the devt, it has finally hit a wall.  I was able to update records via forms I designed, etc... last night - literally out of the blue - i can no longer update one particualr combo box field, nor can I delte a particular record without getting the Could Not Update... message above (in subj title)!  I using a STAND-ALONE, windows XP Media Center PC, am the ONLY user logged in, and am running ONE instance of Access.  

WHAT HAPPENED????  I can't have this... What should I do to tell Access there is no OTHER session - or find out what that seesion is eminating from?  THANKS - I'm in dire straits!
SOLUTION
Avatar of davidW
davidW

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of StuartSanders
StuartSanders

Have you tried a compact and repair?

Also go to tools > options > advanced (tab) and check that the default open mode is shared.

Stuart
Avatar of wintactics

ASKER

Thanks for all the input...

StuartSanders:  I always ensure that shared open mode, and locked edited record are cfg'd... but thanks.

Jokra and DavidW:  I think it has come down to a BAD record corrupting the others... no memo fields... but  I deleted the one record that "started it all" and things seemed fine again.  What's weird is that if I re-add the data (to a new recd), problem comes up again.  There's nothing special or bizarre about the data I'm entering... hate it when this kind of $%@#@ happens.  I'm sure there's a logical explanation... I just can't think of one.  I guess I'm still too green at this.  

Thanks very much for your help guys... when I'm banging my head against this kind of thing, you guys turn the lights back on.  VERY COOL.
You could try writing some code that will loop through the table and copy/insert the data line by line into a new table or database.  If any records are corrupted it might be able to flag them.

Stuart