ODBC Problem with SQL 7.0 SP2

[Brian]

After installed SQL 7.0 Service Pack 2 on our server today, all ADO update
to the same SQL table are getting ODBC error -2147467259. We had no problem
using ADO to update the table before we upgraded. This ADO is launched from
Active Server Page and we had been using it to access the table for awhile
without problem.

Please see attachment for error detail. Do we need to update our ODBC
driver on the as well? The SQL ODBC driver after the upgraded is version
3.70.08.20

Any suggestion?

Thank you.

Brian

begin 666 ODBC Errors.txt
<encoded_portion_removed>

[Patrick Logan]

Have you checked the Connection.Errors collection for any additional
information regarding what it doesn't like? The error number you posted is
a generic E_FAIL message.

--
Patrick Logan, MCSD
Senior Technical Development Advisor
McKessonHBOC -- Extended Care Solutions Group
pat....@hboc.com
Opinions expressed are my own and not necessarily those of McKessonHBOC.

[Brian]

The attachment that I sent from the original e-mail contains all
Connection.Errors from the ODBC. Again, I tried the same ADO from the same
machine with the same ODBC connection BEFORE the upgraded. It ran fine
without any error. I encountered these error AFTER my recordset update the
database. Before the record update the SQL database, the correction error
count was zero.

Any advise?

Brian

"Patrick Logan" <pat....@hboc.com> wrote in message
news:ObfL8SJp$GA....@cppssbbsa02.microsoft.com...

[Brian]

We have set the breakpoint BEFORE recordset Update statement. We also
checked the ODBC Connection.errors count and description before the update
statement. It was zero. Right after the RS.UPDATE statement to update the
SQL 7.0 recordset, we had all ODBC errors from my previous attachment. We
have done the same update BEFORE we upgraded to SQL SP2 and it was fine.

If we are running the ADO on the same machine (NT SERVER) where the WEB
reside and we are using the same ODBC DSN, is it necessary to upgrade the
SQL ODBC system DRIVER? I think the SP2 will take care of the SQL ODBC
driver as well. The driver version is 3.70.08.20 SQLSRV32.DLL dated
10/05/99.

Please advise.

[Patrick Logan]

Sorry, I didn't catch the attachment the first time.

Could you post the SQL statement that is failing or a snippet of your code?
According to the errors, this looks syntax related.

[Patrick Logan]

What is the following line suppose to be doing, it looks "strange"...

oConn.Execute

Should this be Cmd.Execute?

[Brian]

You are right. It should be Cmd.Execute. However, the correction.errors
did not occurred from there. It occurred after the RS.UPDATE statement
later on the page.

Brian
"Patrick Logan" <pat....@hboc.com> wrote in message

news:#YM8LFMp$GA....@cppssbbsa02.microsoft.com...

[Patrick Logan]

I'd have to see from a trace what was actually sent to the server.

[Brian]

Here is the trace after clicking Submit button.

sp_cursor 305520732, 33, 1, N'', 2000, 'Marketing Support', 2000, '20000329
00:00:00:000', 'Joan', 'Marketing', '20000416 00:00:00:000', '11X17 Poster',
'20000515 00:00:00:000', 'No ', 'Marketing', 'No ', 'cc600', 1111, '', '',
'', '', '', '', '', '20000403 00:00:00:000', '20000404 00:00:00:000',
'20000320 00:00:00:000', '20000406 00:00:00:000', '20000407 00:00:00:000',
'20000410 00:00:00:000', '20000411 00:00:00:000', '20000412 00:00:00:000',
'20000413 00:00:00:000', NULL, NULL, NULL, 1, 1, 1, 1, 1, '
', 0x0, '', '', '', 50, 40., 0.80000000000000004, 0., 0., 0., 10, 40., 4.,
0., 0., 0., 80., 0., 75., 0.40000000000000002, 30., 0.69999999999999996, 0.,
52.5, 75., 0.80000000000000004, 60., 0.90000000000000002, 0., 67.5, 30.,
0.90000000000000002, 27., 0.40000000000000002, 0., 12., 30.,
0.29999999999999999, 9., 0.29999999999999999, 0., 9., 0.,
0.20000000000000001, 0., 0.20000000000000001, 0., 0., 0.,
0.80000000000000004, 0., 0.10000000000000001, 0., 0., 0.,
0.90000000000000002, 0., 0.90000000000000002, 0., 0., 4.3000000000000007,
126., 3.5, 0., 0., 206., 141., 1., 0., 2., '', 3., '', 4., '', 5., '', 6.,
21., 227., 142.

Brian
"Patrick Logan" <pat....@hboc.com> wrote in message

news:uTKE2aMp$GA....@cppssbbsa02.microsoft.com...