I have an application that is backended by SQL Server 7. Here are the steps:<BR><BR>1. User selects to add a new record.<BR>2. Page is fired off that creates a recordset using an INSERT<BR>3. On that same page, another recordset is created and uses the MoveLast method assuming the last record is the one just inserted.(*mayday, mayday*)<BR>4. Page is redirected appending the recordID to the url in the form of a querystring.<BR>5. Next page opens with appropriate fields for editing of the new record.<BR>6. Doesn't always work as it should!<BR><BR>I'm no SQL guru and don't play one on T.V. I do understand however that the @@Identity field (autonumber) which is also our recordID, doesn't always necessarily place a new record at the end of the table. Therefore we end up in a bit of a spot at times. How can I get a hold of that inserted record on the next page if I don't know where it is, or what the number is?