I am automating Access 2003 (Server) from another Access 2003 DB (Client).
Depending upon the existence of some objects in the Server DB, the Client
VBA will receive the error:
"-2147417851 - Automation error
The server threw an exception."
I have looked around, and see that this error has cropped up in discussions
My error handler checks for this error code, and resumes succesfully.
The issue I am finding difficult to handle is that if the server throws an
exception, then the process of closing the server fails silently at the end
of the client function, leaving an instance of MSACCESS.EXE running in
memory, but not visible - even if the server is made visible when it is
The code is:
Set oAccess = New Access.Application
' do some automation things here....
' cause the "-2147417851 - Automation error. The server threw an
Set oAccess = Nothing ' <-- after "-2147417851 - Automation error - this
does not end the MSACCESS Server process.
My question is:
Is there a way to ensure the server instance is properly closed?