Re: ADO Recordset Update & SQL Server 2005 ??
- From: "Hung" <dba247@xxxxxxxxx>
- Date: Wed, 6 Sep 2006 14:27:00 -0500
Provider=sqloledb;Data Source=192.168.1.1;
Set RS = Server.CreateObject("ADODB.Recordset")
RS.CursorLocation = 3 'adUseClient
RS.LockType = 4 'adLockBatchOptimistic
RS.cursortype = 3 'adOpenStatic
query = "select column1, column2 from table order by column1, column2"
data sample: column1 = 99.50, column2 = 0
column1 = 93.83, column2 = 0
I have a loop:
rs.activeconnection = nothing 'disconnect the conn
do while not rs.eof
rs("column2") = floor(rs("column1")) <-- this works with sqlserver
2000, but not sqlserver 2005
rs.movenext
loop
rs.sort = "column1, column2" <-- re-sort
function floor(numeric_value)
'return a floor INT of a float or number
end function
--------
I need to do client-side recordset update and sort like that, but not
updating the data back to the table (disconnected recordset). And changing
the query to SELECT column1, ROUND(column2,0) isn't an option.
the IIS box and SQL Server box are separated. The exact same code, if
connected to a sql server 2000 database, would update the value of
rs("column2") correctly. But if I change the connection string to point to
the same database schema/data in sql server 2005, rs("column2") values
always remain 0 (default to 0). That means the rs("column2") =
floor(rs("column1")) statement doesn't work. The only change in the whote
equation would be pointing to either sql server 2000 database or sql server
2005 database, on differnet machines. There's no change in IIS box. Both
connection strings are exactly the same, except for IP number to point to a
different box.
There's no error. It just doesn't do the update as expected.
Any idea? could it be OS patches, if not sql server 2005 is the culprit?
Thanks!
Hung
"Ralph" <nt_consulting64@xxxxxxxxx> wrote in message
news:a8adnfaf8PlLbWPZnZ2dnUVZ_qadnZ2d@xxxxxxxxxxxxxxx
"Hung" <dba247@xxxxxxxxx> wrote in message
news:%236U7Qvc0GHA.5048@xxxxxxxxxxxxxxxxxxxxxxx
I have a line that says:
rs("column_name") = x
this works fine under sql server 2000, but doesn't work with sql server
2005. What's the problem or changes in sql server 2005?
Thanks!
HH
[A little detail on what is not working would have been nice, but...]
Try rs("column_name").Value = x, or the spelling or case.
Look for something in your code. I doubt very much that construct has been
tinkered with. If it was the entire phone system in Redmond would have
been
shutdown long ago. <g>
-ralph
.
- Follow-Ups:
- Re: ADO Recordset Update & SQL Server 2005 ??
- From: Daniel Crichton
- Re: ADO Recordset Update & SQL Server 2005 ??
- From: Ralph
- Re: ADO Recordset Update & SQL Server 2005 ??
- References:
- ADO Recordset Update & SQL Server 2005 ??
- From: Hung
- Re: ADO Recordset Update & SQL Server 2005 ??
- From: Ralph
- ADO Recordset Update & SQL Server 2005 ??
- Prev by Date: Re: ADO memory leak version 2.82.1830.0
- Next by Date: Console output via ADO?
- Previous by thread: Re: ADO Recordset Update & SQL Server 2005 ??
- Next by thread: Re: ADO Recordset Update & SQL Server 2005 ??
- Index(es):
Relevant Pages
|