Hi,

I have an ASP application that accesses an SQL Server 2000 database.

On one of my ASP pages, I want to create a NEW record in a table, and IMMEDIATELY (i.e. in later code on that same page) have access to the primary key of that record.

If I use a primary key that is an auto-generated number (in the database) it seems that my ASP cannot immediately know what that number is. I am therefore forced to use non-auto-generated primary keys in the table, and generate the primary key of the new record manually in the ASP, so that I immediately know what it is.

Is this correct, or is there a better way? Am I missing something? I would prefer it if I can always use auto-generated primary keys in my tables.

Hope you can help.

Thanks.

Steve

P.S. The auto-generated primary keys that I am taking about are sequential integers.

best practice is to use a stored procedure to create the record and return the value of @@IDENTITY as an output parameter

hth
Phil

hi,

Another alternative is to use the serverside cursor instead a client side
Write something like this before opening the connection

MyCon.CursorLocation=aduseServer
Mycon.open "Provi....... etc.

After that open a dynamic cursor based recordset for adding a new row
Add values in the field and call update method. Just after update you can access the value of autogenerated value from the field without closing the recordset.

cheers

Anubhav Kumar