Error 3211 Database Engine Could Not Lock Table...

Question

...because it is already in use by another person or process"
I have a procedure that creates a temporary table in Access and fills it from a SQL Server query via an ADO recordset. The temp table is then used as the recordsource for a bunch of reports.
The Create and Fill work fine. The problem occurs when I attempt to DROP the table before it's created (I do this rather than delete the rows because I keep changing the table schema and this way I only have to make the change in SQL; also I think it cuts down
on bloat).
Here's my code section:
    On Error Resume Next
    sqlStr = "DROP TABLE " + LocalTblName
    dbCurrent.Execute (sqlStr)
    If Err.Number > 0 Then 'should fall through here if the table doesn't exist, or if it's locked
        Debug.Print "utl_ADO.CreateTableFromADORecordset: Couldn't drop table " + LocalTblName + ", so clear it and refill it"
        utlClearTableRows LocalTblName, "All"
        GoTo FillerUp
    End If
I close the report that's bound to the temp table, then re-run the program to bring up another set of data. When it hits the DROP TABLE I get different behavior on 2 different PCs - one is my development PC at home, the other is a PC at work. Both run Access2010.
1. At home: Access throws Error 3211 every time. However, the RESUME NEXT allows the error to fall through, whereupon I just do a DELETE from the temp table and then refill it, so it effectively works as long as I don't alter the table schema. The question
is why is the table still "locked" after the report is closed?
2. At work: Access hits the dbCurrent.Execute (sqlStr) and doesn't RESUME NEXT. Instead, it throws up the Error 3211 dialog box and stops. However, if I close the error dialog and re-execute the code, it DROPs the table without throwing an error. The weird
thing is that it alternates between failing and succeeding every other time it executes! So, my question is twofold: a) why doesn't the execution RESUME after the error like it does on my home PC?, and b) why does it succeed only after first failing each time?   
Darrell H Burns

Answer 1

Hi Darrell H Burns,
Thank you for posting in the MSDN Forum.
I'm trying to involve some senior engineers into this issue and it will take some time. Your patience will be greatly appreciated.
Sorry for any inconvenience and have a nice day!
Regards & Fei
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.