I can post more source code if you want to see it. In the Insert procedure, the line returning the identity was: SELECT CCARD_TRANS_ID = @@IDENTITY but should be: SELECT @CCARD_TRANS_ID = @@IDENTITY Strangely enough, fixing that makes it Thanks~! You may have to register before you can post: click the register link above to proceed.

Check the DS PAR for the version supported by DS what is you DS version ? These kinds of error messages are generated at different levels of the ODBC interface. We can see tables, even see data in the designer, and our DBA has confirmed he saw our user log in when we execute a job. Changed database context to 'master'. (5701) hidenori05-17-2006, 01:38 PMWhat version of MDAC do you have on the client machine?

MS SQL Server SQL - The SELECT Statement Video by: Zia Viewers will learn how to use the SELECT statement in SQL and will be exposed to the many uses the The Client will sometimes suppress such warnings if they are expected; in all other cases, these warnings are displayed. followed by Error # = 0 Description = [Microsoft][ODBC SQL Server Driver][SQL Server]Changed language setting to us_english. They either succeed or fail.

koen0105-17-2006, 02:01 AMBy looking at the logging, I found the problem. using SQL 7 Stored Proc's I'm trying to use SQL 7 stored procedures to implement something like example B7 where I allow users to signon and only show them to update It's confusing that not the real error is displayed.

In an old VB6 application, I added a call to a new INSERT stored procedure that I created, for a table I also created. We are on XI 3.0. All Rights Reserved. Each of these errors includes an SQLSTATE that provides detailed information about the cause of a warning or error and a diagnostic message that includes a native error code (generated by