CALL OPENDATACON
DIM RS
SET RS=SERVER.CreateObject ("ADODB.RECORDSET")
s="select * from dbpassenger order by ref_no"
CALL OPENRS(RS,S)
DIM RS1
dim aa
SET RS1=SERVER.CreateObject ("ADODB.RECORDSET")
s="select * from dbfare where flight_id='" & session("fid") & "'"
CALL OPENRS(RS1,S)
if rs.RecordCount >0 then
rs.MoveLast
aa=rs("ref_no") + 1
else
aa=1
end if
session("ref_no")=aa
DIM XX
xx=0
<% if len(trim(request("txtfname1")))>0 then
RS.AddNew
rs("ref_no")=CINT(aa)
rs("flight_id")=session("fid")
rs("first_name")=request("txtfname1")
rs("last_name")=request("txtlname1")
rs("sex")=request("sex1")
rs("age")=request("TXTage1")
if request("TXTage1")<12 then
xx=xx+rs1("fare_child")
else
xx=xx+ rs1("fare_adult")
end if

jksharmadelhi [at] gmail.com wrote:
> CALL OPENDATACON
The rest of this code is irrelevant. The relevant part is in that
opendatacon sub. See here:

http://www.aspfaq.com/show.asp?id 62

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

Bob wrote on Sun, 6 May 2007 18:44:25 -0400:

> jksharmadelhi [at] gmail.com wrote:
>> CALL OPENDATACON
> The rest of this code is irrelevant. The relevant part is in that
> opendatacon sub. See here:
>
> http://www.aspfaq.com/show.asp?id 62
>


I'd say it's in the OPENRS function - that's where the recordset is created,
and so will likely be where the additional properties need setting to make
the recordset updateable.

Dan

Daniel Crichton wrote:
> Bob wrote on Sun, 6 May 2007 18:44:25 -0400:
>
>> jksharmadelhi [at] gmail.com wrote:
>>> CALL OPENDATACON
>> The rest of this code is irrelevant. The relevant part is in that
>> opendatacon sub. See here:
>>
>> http://www.aspfaq.com/show.asp?id 62
>>
>
>
> I'd say it's in the OPENRS function - that's where the recordset is
> created, and so will likely be where the additional properties need
> setting to make the recordset updateable.
>
It may, but in my experience, "updatable cursor" problems, unless being
caused by the SQL being used to open the recordset (multiple tables being
joined, calculated columns), are almost always caused by lack of permissions
for the folder containing the database, as described in the article.

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"