Rob Rudloff
asked on
VB6/SQL getting "Changed language setting to us_english" with one procedure
Hi.
In an old VB6 application, I added a call to a new INSERT stored procedure that I created, for a table I also created. I copied the formats from an existing one that works (and you can see them, attached as .sql files)
When VB6 executes the call to the proc, it returns two VB6 errors:
VB6 error 5703, which shows as:
Even though I get this error back from my new procedure only, I have checked my user language settings, which point to English (picture attached).
Why would I get this behavior on only this one procedure?
I can post more source code if you want to see it.
Thanks!
CREATE-TABLE.sql
CREATE-PROC.sql
In an old VB6 application, I added a call to a new INSERT stored procedure that I created, for a table I also created. I copied the formats from an existing one that works (and you can see them, attached as .sql files)
When VB6 executes the call to the proc, it returns two VB6 errors:
VB6 error 5703, which shows as:
Error 01000: [Microsoft][SQL Server Native Client 10.0][SQL Server] Changed language setting to us_english.
VB6 error 5701: Error 01000: [Microsoft][SQL Server Native Client 10.0][SQL Server]Changed database context to 'ProdDB'.
(I know that they are really not "errors" in SQL, but the existing VB6 code sees them as such.)Even though I get this error back from my new procedure only, I have checked my user language settings, which point to English (picture attached).
Why would I get this behavior on only this one procedure?
I can post more source code if you want to see it.
Thanks!
CREATE-TABLE.sql
CREATE-PROC.sql
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The actual error was a typo in my original SQL procedure, as described above.
USE ProdDB
Create procedure...