Insert and update problems with OLEDB driver

Cos · September 22nd, 2003, 07:40 AM

Hi

First i wanna say hi since this is my very first topic in this forum.

Now let's get to the subject.

I have some problems with my scripts and I hope to get an answer here. My script supposed to make an easy task. An insert into a table. And it worked very well until I changed the ODBC drivers from M$ into OLEDB drivers from IBM.

This is the part of the script where I get the error:

-----------
set objNouvCde = Server.CreateObject("ADODB.Recordset")
objNouvCde.Open "DRW01FIC.DRTCDE", objConn, 2 , adLockPessimistic, adCmdTable
objNouvCde.AddNew
....

-------------

It works very well with this connection string :

"Provider=MSDASQL.1;Password=***;Persist Security Info=True;User ID=user;Data Source=DSN1"

but when I am using the OLEDB driver the connection string gets :

"Provider=IBMDA400.DataSource.1;Password=***;Persi st Security Info=True;User ID=user;Data Source=DSN2"

The error I get is

"ADODB.Recordset (0x800A0CB3)
Current Recordset does not support updating. This may be a limitation of the provider, or of the selected locktype."

Can anyone help? Is there some driver limitation and I can't get Dynamic cursor or stuff like that?

I am on a Windows 2000 server with IIS 5.0 and the DB is DB2/AS400

Thanks

Linux is like a wigwam : no windows, no gates, apache inside.

RODEO · September 24th, 2003, 01:50 AM

I know that, in VB6 with standard ADO (not .NET), you had to specify a Command Object, with the following Properties

Quote:

quote:
'Constants
Public Const DBPROPVAL_UP_CHANGE = 1
Public Const DBPROPVAL_UP_DELETE = 2
Public Const DBPROPVAL_UP_INSERT = 4

'Connection, Command and Recordset objects
        sConnectionString = "Provider=IBMDA400;Data Source=" & System & ";Transport Product=Client Access;SSL=DEFAULT"
        With cn
            .CursorLocation = adUseServer
            .Open sConnectionString, UserID, PWD
        End With
    With cm
        .ActiveConnection = cn
        .Properties("Updatability") = DBPROPVAL_UP_CHANGE + DBPROPVAL_UP_INSERT + DBPROPVAL_UP_DELETE
        .CommandText = sSQL
    End With
    rs.Open cm.CommandText, cn, adOpenStatic, adLockReadOnly

I'm also still struggling with reproducing this in ADO.NET...:(

But then again, that's the fun of the job;)

The further away I get from the things I care about,
The less I care about how much further away I get

RODEO · September 24th, 2003, 01:52 AM

LOL, opening the RS ADLOCKREADONLY would of course make little sense here :-)

The further away I get from the things I care about,
The less I care about how much further away I get