Solved

Get newly created ID in SQL Server

Posted on 2008-10-22
12
445 Views
Last Modified: 2012-06-27
Hi

I am building an MS Access/SQL Server app.  If I create a new record  in the SQL Server backend using VBA behind an Access form how can I get the newly created ID and return it to Access?

Cheers
0
Comment
Question by:kenabbott
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 4
  • 2
  • +1
12 Comments
 
LVL 11

Expert Comment

by:Muhammad Kashif
ID: 22774411
Use
Select @@IDENTITY


You can use like this with your insert query

Insert into Table values(1,2,.....)
Select @@IDENTITY
0
 
LVL 22

Accepted Solution

by:
dportas earned 500 total points
ID: 22774570
Use SCOPE_IDENTITY() wherever possible rather than @@IDENTITY.

SCOPE_IDENTITY() returns the last inserted IDENTITY value in the current scope, which means its behaviour won't be affected by any current or future triggers on the table. If you are using SQL stored procs for data access then SCOPE_IDENTITY() should normally be preferred over @@IDENTITY.
0
 

Author Comment

by:kenabbott
ID: 22774728
So is the only way of doing this via a stored procedure??  Its not by getting a returned value with a pass thru query for example
0
Why You Need a DevOps Toolchain

IT needs to deliver services with more agility and velocity. IT must roll out application features and innovations faster to keep up with customer demands, which is where a DevOps toolchain steps in. View the infographic to see why you need a DevOps toolchain.

 
LVL 84
ID: 22774911
How are you creating the new record? Show the relevant portion of the code.

Does the Jet/OLEDB provider support SCOPE_IDENTITY? I'm not sure ... I know it supports IDENTITY:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;232144

But I've not found an article stating it supports SCOPE_IDENTITY. That said, you could of course get this via a Stored Proc or something ...
0
 

Author Comment

by:kenabbott
ID: 22774950
At the moment I'm still working on this but basically what I need to achieve is as follows...

1.  User enters data onto an access form
2.  Data saved in SQL as new record
3.  New ID returned
4.  New ID saved in a seperate SQL table (along with other data)

0
 
LVL 84
ID: 22774982
Again: How are you creating the new record? Are you using bound forms? If you are then your Form's Recordset will contain the new value after saving ...
0
 

Author Comment

by:kenabbott
ID: 22774998
Sorry - no it is an unbound form so I will be using a SQL statement of some sort
0
 
LVL 84
ID: 22775031
I'd certainly agree with dportas as to using SCOPE_IDENTITY, but as I said earlier I'm not sure it's supported. You could do this:

Dim rst As ADODB.Recordset
Dim lNewID As Long

<Insert your record>

Set rst =New ADODB.Recordset
rst.Open "SELECT @@IDENTITY AS NewID", YourConnectionObject
lNewID = rst("NewID")

This could run into issues if you have a lot of users banging away on this, since as others have said @@IDENTITY gets the last inserted value - so if you insert your record, and then I insert a record immediately after that BEFORE YOUR CALL TO @@IDENTITY then you'll get the ID of the record I inserted. If you use a Stored Proc, you can use SCOPE_IDENTITY, which insures that you get the correct value.

0
 
LVL 22

Expert Comment

by:dportas
ID: 22777043
@@IDENTITY is scoped to the connection so you will never get the identity value of a row inserted by someone else unless you are connection pooling.

0
 
LVL 84
ID: 22777128
Good to know ...
0
 
LVL 84
ID: 23040940
So why did you accept the SCOPEIDENTITY answer? Is that what you ended up using?
0
 

Author Comment

by:kenabbott
ID: 23042464
yes
0

Featured Post

Revamp Your Training Process

Drastically shorten your training time with WalkMe's advanced online training solution that Guides your trainees to action.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

AutoNumbers should increment automatically, without duplicates.  But sometimes something goes wrong, and the next AutoNumber value is a duplicate.  This article shows how to recover from this problem.
Access developers frequently have requirements to interact with Excel (import from or output to) in their applications.  You might be able to accomplish this with the TransferSpreadsheet and OutputTo methods, but in this series of articles I will di…
Basics of query design. Shows you how to construct a simple query by adding tables, perform joins, defining output columns, perform sorting, and apply criteria.
Using Microsoft Access, learn some simple rules for how to construct tables in a relational database. Split up all multi-value fields into single values: Split up fields that belong to other things into separate tables: Make sure that all record…

738 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question