RE: SQL Server 2000 and @@Identity

Try putting this into a stored proc and trying it. I am using SQL 2000 and I have no problem doing this. Clint -Original Message- From: Rick Walters [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 11, 2002 2:02 PM To: CF-Talk Subject: SQL Server 2000 and @@Identity Hi List, I

RE: SQL Server 2000 and @@Identity

try upgrading your mdac. also why aren't you delcare lastid and making your statement SELECT @lastid = @@identity Anthony Petruzzi Webmaster 954-321-4703 [EMAIL PROTECTED] http://www.sheriff.org -Original Message- From: Rick Walters [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 11,

RE: SQL Server 2000 and @@Identity

Checking on the MDAC upgrade idea.. @lastid would assume lastid is a declared variable, it's just part of my select statement. I could have named it anything. Thanks for the MDAC idea. It's a new server and I forgot about that. Good Fortune, Richard Walters, Webmaster, Davita Laboratory

RE: SQL Server 2000 and @@Identity

also why aren't you declare lastid and making your statement SELECT lastid = identity If he did that, he wouldn't get lastid back as a query column. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444

RE: SQL Server 2000 and @@Identity

, April 11, 2002 3:36 PM To: CF-Talk Subject: RE: SQL Server 2000 and @@Identity also why aren't you declare lastid and making your statement SELECT @lastid = @@identity If he did that, he wouldn't get lastid back as a query column. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice

RE: SQL Server 2000 and @@Identity

also why aren't you declare lastid and making your statement SELECT lastid = identity If he did that, he wouldn't get lastid back as a query column. I usually use SET NOCOUNT ON INSERT INTO people (password, username) VALUES ('something', 'testuser123456')