Error: "01000: Changed language setting to us_english."

Question

Users occasionally get this message through the application, but I have been unable to reproduce it, and it seems entirely random.  I know that it is informational only, but the application is reporting it as an error.  I had assumed it was coming back with a number of 0, so I trapped that (If Err.Number = 0...), but this just happened again, and clearly it is not that.

So, I was wondering if anyone actually *knows* what error number this returns.  I "believe" it may be 5701, but I cannot verify that, since I cannot reproduce it.  Also, if anyone knows how I can force this message, I would appreciate that as well.

And yes, I know I could trap it by checking the description, but I would rather use the number if at all possible.

Any help is much appreciated :)

Answer 1

That looks like a VB6 ODBC problem (Err.Message is VB6, 5701 refers to ODBC SQL connection information message).

If that is so then this not the right forum - it's VB.Net. I'd try a VB forum.

---

Regards David R
---------------------------------------------------------------
The great thing about Object Oriented code is that it can make small, simple problems look like large, complex ones.
Object-oriented programming offers a sustainable way to write spaghetti code. - Paul Graham.
Every program eventually becomes rococo, and then rubble. - Alan Perlis
The only valid measurement of code quality: WTFs/minute.

Answer 2

Yes, the app is VB6, but all the information I'd found on the issue was pertaining to .NET, so I'd assumed it would still be the same VB error number.  I will try a forum specific to VB6.

Thanks.

Answer 3

VB.Net tends not to use error numbers (not even sure they still exist, or are easily found if they do). Instead it uses Exceptions and Exception handling (try...catch... blocks) to deal with errors.

---

Regards David R
---------------------------------------------------------------
The great thing about Object Oriented code is that it can make small, simple problems look like large, complex ones.
Object-oriented programming offers a sustainable way to write spaghetti code. - Paul Graham.
Every program eventually becomes rococo, and then rubble. - Alan Perlis
The only valid measurement of code quality: WTFs/minute.

Answer 4

Yes, I actually rather prefer .NET, but I work on what I am told to work on, which (for now at least) is a VB6 project.  I am quite familiar with the try/catch blocks, but the Err object does exist in .NET, so I assume all the properties still return the same way.