@@IDENTITY for Access -- Is it thread safe?

Is @@IDENTITY thread safe in that it returns the autoincrement value for the
most recent insert for that thread or just the most recent insert by any
thread?

Tim says @@IDENTITY works with ADO and but not DAO. What about ODBC?

I'm looking at
http://msdn.microsoft.com/library/de...asp?frame=true
and I'm very confused! I'm sure that MS Access does not, for example,
support stored procedures.

Tim says there are a lot of TSQL features supported in MS Access. Is there a
list somewhere?

I'm looking at Dino "Building Web Solutions with ASP.NET and ADO.NET" and I
see really fancy SQL like

SELECT
CASE GROUPING(o.customerid) WHEN 0 THEN o.customerid ELSE '(Total)' END
AS AllCustomerSummary,
CASE GROUPING (os.orderid) WHEN 0 THEN od.orderid ELSE -1 END
AS IndividuallyCsutomerSummary,
FROM Orders o, [Order Details] od
GROUP BY o.customerid, od.orderid WITH ROLLUP

Will these fancy keywords like CASE and ROLLUP work in MS Access?

There used to be MSAccess SQL syntax at search.microsoft.com but I cannot
find it anymore.

Thanks,
Siegfried


Could someone kindly point me to the URL on the SQL syntax for
MSAccess and specifically where the IDENTITY keyword is documented?


Quite right: it's @@IDENTITY. Look here

http://doc.ddart.net/mssql/sql70/globals_7.htm

or search the MSDN site too.

B Wishes


Tim F

"Siegfried Heintze" wrote in
:

I'm confused! This is for T-SQL (aka MS SQL Server). Does this also
work for MSAccess?

Yes, as long as you use the ADO library (not DAO, which was never updated
to Jet 4). I'm not completely sure that ADO/T-SQL handles the entire SQL
syntax, but most everyday things like @@IDENTITY, CHECK constraints,
DEFAULT values and so on are there.

That is why the answer to the question "Is DAO better for Access + Jet than
ADO" is, "Yes, except for..." Nothing in life is ever straightforward!

Best wishes


Tim F