experts ONLY; IDENTITY microsoft ole db provider for SQL Server
- From: ftq@.
- Date: Wed, 22 Feb 2006 07:23:29 GMT
This function through and .asp page, not .aspx
This function runs with the LATEST ado version or "whatever" and
connects to a FULLY patched SQL server 2000 running at alentus.com ...
Function SaveOrderData(byval idCustomer, byval idOrder)
Dim rs
Set rs = Server.CreateObject("adodb.recordset")
rs.CursorLocation = adUseClient
rs.Open"orders"[connection string], adForwardOnly,
adLockOptimistic)
rs.Update
SaveOrderData = rs("idOrder")
Set rs = nothing
End Function
If I use rs.CursorLocation = adUseClient , will I have an @@IDENTITY
"crisis" when handling aLOT of order insert requests from the website
server? j
OR
Must I change my code to "requery" the server or some ***? By
default the ado is set to "serverSide"... because I set my rs to
client side can I be guaranteed that I got the correctly inserted
@@IDENTITY number?
p.s. - this is a freshly imported DB from an Access 2000 file... there
are no triggers or *** like that yet...
.
- Prev by Date: Retrieving hyperlink url from Excel spread***
- Next by Date: MDAC 2.7 with Win XP SP2
- Previous by thread: Retrieving hyperlink url from Excel spread***
- Next by thread: MDAC 2.7 with Win XP SP2
- Index(es):