3262 or 3211 in a docmd.runsql
Access 2002 (XP).
I am trying to sort out someone else's Access system and one of these errors occurs - not sure which but they both mean it could not lock the target table - I assume it would not need to lock the tables it is select-ing from... There is no-one else using the target table at the time. IS there a quick way to unlock a table when it has been left lying around locked and you don't know why?
Many thanks.
I am trying to sort out someone else's Access system and one of these errors occurs - not sure which but they both mean it could not lock the target table - I assume it would not need to lock the tables it is select-ing from... There is no-one else using the target table at the time. IS there a quick way to unlock a table when it has been left lying around locked and you don't know why?
Many thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The ACcess process may still be running from a previous corrupt instance and locking your file.
To delete any previous instances:
Close MS Access.
Use CTRL+ALT+DEL and select TASK MANAGER
Select PROCESS Tab.
RIGHT click and END PROCESS TREE for any instances of MSACCESS.EXE
To delete any previous instances:
Close MS Access.
Use CTRL+ALT+DEL and select TASK MANAGER
Select PROCESS Tab.
RIGHT click and END PROCESS TREE for any instances of MSACCESS.EXE
ASKER
I sorted it by creating an empty db and importing everything from the original problem db to it. That solved the problem but all sorts of other things stopped working that were ok in the orginal. Any guesses as to why this might be? I would think that if everything was copied over, it should work like the original...
peter
peter
'all sorts of other things stopped working '
You have to be specific.
There is no general problem in importing from another db
Pete
You have to be specific.
There is no general problem in importing from another db
Pete
No. You cannot unlock a table - you have to remove the condition that is causing it to be locked.
In a single user situation this could be because the user has more than one form/query/table/report open at the same time.
Pete