:) I found the problem.
It was related to running a procedure querying an Excel file with ODBC connection: ODBC;Driver={Microsoft Excel Driver (*.xls)}...
Although the procedure runs fine and ends with no errors, it is generating an memory error that is just evident when closing the Excel application, even with no error/alert message from Excel, besides the VBAProject Password one (if the project is not protected, you do not get that form).
I am using and ADODB connection now with no other issues.
JD
|