Hi List,
I recently upgraded from SQLServer7 to 2k and the @@identity in the
code below now returns a null string. Anyone know why this might be
happening?
code block~~
!--- insert user info ---
cfquery name=insertPeople datasource=#dsn#
set
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
, 2002 3:02 PM
To: CF-Talk
Subject: SQL Server 2000 and @@Identity
Hi List,
I recently upgraded from SQLServer7 to 2k and the @@identity in the
code below now returns a null string. Anyone know why this might be
happening?
code block~~
!--- insert user info
Message-
From: Rick Walters [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 11, 2002 3:02 PM
To: CF-Talk
Subject: SQL Server 2000 and @@Identity
Hi List,
I recently upgraded from SQLServer7 to 2k and the @@identity in the
code below now returns a null string. Anyone know why this might
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
, 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
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')
7 matches
Mail list logo