ODBC connection help

I have a very old asp/java web application running on windows server 2008 r2.  The application uses the 32 bit ODBC connection to read/write to sql 2000 database on another server.  I can read from the database but it can't  right (the application on the original server is running just fine and is in use).  Does the native client for Windows server work for SS2000, or is there a way to install a back-versioned client?
dhenderson12Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

QlemoBatchelor, Developer and EE Topic AdvisorCommented:
Yes, the W2008r2 ODBC driver for SQL Server should be 2000 one (looked that up on our server). The driver release is 6.01.*, dated in 2010.
Not being able to write to the DB sounds strange, as there is nothing like a R/O driver or setting for MSSQL. Do you get something useful as error message?
0
arnoldCommented:
You need to use odbctab32 to set up the32 bit ...

Is the asp or the Java one has the issue? Usually, the newer version is backwards compatible.

Can you setup a test.asp using dsnless connection to the SQL 2000 to see what error if any in write you get?
Any chance of upgrading to SQL 2005 the db can still be configured in SQL 2000(8.0) version.

Test the newer SQL server, with your asp/Java ......m sql2008 might also support the 8.0 mode.

You could install the 9.0 SQL native client to try, switch the dsn to use SQL bat ice client 9.0 versus 10.x
0
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
arnold, odbcad32 is the name both of the 64 (in %WinDir%\System32) and the 32bit (in %WinDir%\SysWoW64) exe. And the integrated MSSQL driver is installed and working identically for both. And if you read the question again, you'll see the OP can connect to and read from the ODBC source.

Of course installing another release of the MSSQL driver can be a change, but I doubt that. And you need to have the client available.
0
arnoldCommented:
You need to run. The 32bit one to configure the 32but dsn connection....
I saw the read part, no error checking/detecting seemingly to indicate why the write is failing.


One can still download the 2005 client, I think it is available as a download.

There is a disconnect in theinformation. ...
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
dhenderson12Author Commented:
thanks, guys, for the help.  the biggest issue was there is a 64-bit AND a 32-bit that we have to keep in sync.  my bad, that's why I'm splitting the points, since you both took time.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
ASP

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.