Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

How can I downgrade my ODBC drivers?

3,358 views
Skip to first unread message

Christoph Nievergelt

unread,
Mar 24, 1999, 3:00:00 AM3/24/99
to
Hi
I made the mistake of installing-uninstalling Interdev from VS 6.0 (just to get the s/n to order my service pack) on my NT WS with the ODBC drivers for SQL Server 6.5 (2.65..) and ended up with new ODBC drivers (SQL: 3.60.319).
Now I am having the problem that one of my Recordsets is marked as not updateable and I suspect these to facts to be correlated.
However I cannot find a way to get back my old drivers.

Can anyone give me hint, please.

Share and Enjoy Christoph Nievergelt

noel.sc...@bankfirstcorp.com

unread,
Mar 24, 1999, 3:00:00 AM3/24/99
to
In article <7dahh1$4ba$1...@dino.active.ch>,

"Christoph Nievergelt" <ChNiev...@zsd.ch.spam> wrote:
> Hi
> I made the mistake of installing-uninstalling Interdev from VS 6.0 (just =
> to get the s/n to order my service pack) on my NT WS with the ODBC =
> drivers for SQL Server 6.5 (2.65..) and ended up with new ODBC drivers =
> (SQL: 3.60.319).
> Now I am having the problem that one of my Recordsets is marked as not =

> updateable and I suspect these to facts to be correlated.
> However I cannot find a way to get back my old drivers.
>
> Can anyone give me hint, please.
>
> Share and Enjoy Christoph Nievergelt
>
>

Here's how you can go back to an older SQL Server driver.

1) Unregister the existing SQL Server driver as follows...

regsvr32 /u- fullpath\SQLSRV32.DLL

(fullpath will probably be "C:\windows\system" or "C:\winnt\system32")

2) Rename SQLSRV32.DLL v3.6 to something else so you still have it if you need
it down the road.

3) Copy SQLSRV32.DLL v2.65 to the same directory v3.6 was located.

4) Register the v2.65 SQL Server driver as follows...

regsvr32 fullpath\SQLSRV32.DLL

HTH, it worked for me.

Noel

-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own

Erik Klein

unread,
Mar 24, 1999, 3:00:00 AM3/24/99
to
The driver is only used for access and should effect the data itself. I
would check other avenues......
Christoph Nievergelt wrote in message <7dahh1$4ba$1...@dino.active.ch>...
Hi
I made the mistake of installing-uninstalling Interdev from VS 6.0 (just to
get the s/n to order my service pack) on my NT WS with the ODBC drivers for
SQL Server 6.5 (2.65..) and ended up with new ODBC drivers (SQL: 3.60.319).

Now I am having the problem that one of my Recordsets is marked as not

Christoph Nievergelt

unread,
Mar 24, 1999, 3:00:00 AM3/24/99
to
Thank you for your input. regsvr32 did not work for me, I got a dialog telling me
something about a corrupt version in memory.

However, when I just replaced the driver (the old DLL was still there with a .001 extension) and
rebooted, I was back.

Now the debug message telling me to call my system support to upgrade the SQL Server ODBC
procedures has gone. However, I *still* get the messages that the driver changes cursor concurrency
and finally one telling me (for the last of my RecordSets that I open!):
Marking CRecordset as not updatable.

Share and Enjoy Christoph Nievergelt


noel.sc...@bankfirstcorp.com schrieb in Nachricht <7daujc$67v$1...@nnrp1.dejanews.com>...


>In article <7dahh1$4ba$1...@dino.active.ch>,
> "Christoph Nievergelt" <ChNiev...@zsd.ch.spam> wrote:

>> Hi
>> I made the mistake of installing-uninstalling Interdev from VS 6.0 (just =
>> to get the s/n to order my service pack) on my NT WS with the ODBC =
>> drivers for SQL Server 6.5 (2.65..) and ended up with new ODBC drivers =
>> (SQL: 3.60.319).
>> Now I am having the problem that one of my Recordsets is marked as not =


>> updateable and I suspect these to facts to be correlated.
>> However I cannot find a way to get back my old drivers.
>>
>> Can anyone give me hint, please.
>>
>> Share and Enjoy Christoph Nievergelt
>>
>>
>

Christoph Nievergelt.vcf

Christoph Nievergelt

unread,
Mar 24, 1999, 3:00:00 AM3/24/99
to
Searching MS KB with 'Marking CRecordset as not updatable' I found the relevant article:

Summary: If you want to use a dynaset you have to have an unique index on the table.

So I just change the Recordset to snapshot!?
Yes, *but* you need a CDatabase object that you open with option CDatabase::useCursorLib,
otherwise you get told that the driver does not support that option <g>.

Share and Enjoy Christoph Nievergelt


Christoph Nievergelt schrieb in Nachricht <7db468$d3s$1...@dino.active.ch>...

Christoph Nievergelt.vcf
0 new messages