We have a C++ dll used in an external name clause in an SQL Anywhere 10 function. It calls a .Net C# dll. When both dlls are placed in the ASAwin32 folder, all works well. The return string from the .Net dll gets returned to the C++ dll and in turn to the SQL function. We would like not to put dlls in the ASAwin32 folder. But when I put the dlls in some other folder that is in the path, it kills the database. I've been testing calling the SQL function from ISQL, and ISQL returns and ISQL Error message box with "Error! The connection to the database was closed by the server. Communications error SQLCode=-85, ODBC 3 State="08S01"." Any thoughts on why this would happen?
asked 01 Nov '11, 12:59