It is likely that a descriptor and memory leak in the MaxDB ODBC driver on Wondows 2000 .
So, the number of descriptors and allocate memory in test process in Windows system monitor before performing and after that get the increase first once in 82 but then in 4 descriptors on every Open/Close operation. May be it not be very danger on client applications, but not good for server with ODBC connection. I was testing in MFC program with CDatabase class and pure ODBC program with next function sequence: Open: SQLAllocEnv SQLAllocConnect SQLConnect SQLAllocStmt Close: SQLFreeStmt(this->m_hStmt,SQL_CLOSE); SQLDisconnect(this->m_hDbc); SQLFreeConnect(this->m_hDbc); SQLFreeEnv(this->m_hEnv); P.S. Why change order of database and server name fields in ODBC 7.5 data source admin window? Please, change the TAB order too or return as be earlier. __________________ Pavel Konovalov http://www.rscom.ru -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
