Hi,
In moving a working data warehouse solution in SQL Server 2000 from Windows 2000 Server (32 bit) to Windows 2003 Server Enterprise Edition x64 edition, we are finding that we are unable to access the database.
Is this due to not using a 32bit ODBC driver ? Is there a specific MDAC version or SQL Server 2000 SP we should be using?
Much appreciated,
Julie
Hello,
I am having problem with our network. We run a clinic database system that uses SQLServer 2000 Enterprise as the backend, and Microsoft Access on the front end.
I have had a running problem with all our newer machines (which run Windows 2000 or XP) in that while it connects to the server and retrieves some of the info properly, on some of the pages it doesnt. It will take 2 or 3 minutes for a page of the database to load, and even then not all the information will be retrieved properly.
I was able to fix the problem on the Windows 2000 machines by replacing the Sqlsrv32.dll file with an older version (usually with 3.70.06.23). And then the W2000 machines would work. But for some reason, the XP machines wont accept the older sqlsrv32.dll file...it gives me this error:
SQLState: 'HY000'
SQL Server Error: 126 Unable to load communication module driver correctly.
....and i cant seem to downgrade the MDAC....
any ideas on what I can do?
thanks
I'm trying to retrieve native character data (SQL_WCHAR) through ODBC into an SQL_C_CHAR buffer using SQLBindCol and SQLFetch.
The database is SQL Server 2005 Developer Edition.
If I use DRIVER={SQL Server}, i.e., use SQLSRV32, everything gets converted properly.
If I use DRIVER={SQL Native Client}, i.e., use SQLCNLI, I apparently get garbage. This is true for ntext, nchar and nvarchar. I also have problems with xml, but I haven't gotten far enough to isolate what's going on with it.