Thanks for the response.
My code creates a query on the fly. When the user is finished the query is deleted. It is ok as long as runtime errors do not show. The problem happen recently when the application is used in Access 2000. A runtime error 2486 "Access is busy". I usually kill Access by going to Task Manager. When running the application after killing it, the application never had chance to delete the query. I have found some code to check for the query, but it bombed when the query didnot exist. Here is the code:
If curdb.QueryDefs("qryCreate Current Date").Name = "qryCreate Current Date" Then
DoCmd.DeleteObject acQuery, "qryCreate Current Date"
End If
Note: The application was created in Access 2003, but used by Access 2000 users.
|