I've been experimenting with your MaxDB data provider as a way of possibly eliminating a memory lead that occurs when I use the standard .NET ODBC library. Everything seems to work fine as long as I'm only communicating to a database hosted in the Windows environment. But when I attempt to use the data provider to connect to a database running on a Solaris machine an exception (data overflow exception)when attempting to open the connection.
I tried to track down the error by importing the source code for your provider into the project and debugging and it appears that the header buffer data is in a different format from the Windows database server. This was using the SAFE mode.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The MaxDB protocol is byte-order specific. I have access to the little-endian x86 hardware only, so an additional testing with big-endian Solaris/Sparc is required. Could you help me in such a staff?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've been experimenting with your MaxDB data provider as a way of possibly eliminating a memory lead that occurs when I use the standard .NET ODBC library. Everything seems to work fine as long as I'm only communicating to a database hosted in the Windows environment. But when I attempt to use the data provider to connect to a database running on a Solaris machine an exception (data overflow exception)when attempting to open the connection.
I tried to track down the error by importing the source code for your provider into the project and debugging and it appears that the header buffer data is in a different format from the Windows database server. This was using the SAFE mode.
The MaxDB protocol is byte-order specific. I have access to the little-endian x86 hardware only, so an additional testing with big-endian Solaris/Sparc is required. Could you help me in such a staff?