| | | | | Browse by category |
Article ID: 877
Last updated: 05 Feb, 2008
Problem
User gets a Sybase warning: Changed database context to... from their error handler.
Cause
This is a harmless warning. Sybase provides this as an informational message any time you log into a different database (context). DBTools.h++ passes all server messages through to the error handler, including this informational warning.
Action
User gets a Sybase warning: Changed database context to... from their error handler.
Cause
This is a harmless warning. Sybase provides this as an informational message any time you log into a different database (context). DBTools.h++ passes all server messages through to the error handler, including this informational warning.
Action
As a work around to avoid these messages you could do something like this
In you errorhandler
void OutputDBStatus (const RWDBStatus& aStatus)
{
if(aStatus.vendorError1() == 5701)
;
else
{
// Print out the error.
cerr << "Error code:" << (int) aStatus.errorCode() << endl
<< "Error message " << aStatus.message() << endl
<< "Is terminal: " << (aStatus.isTerminal()? "Yes" : "No")<< endl
<< "Vendor error 1:" << aStatus.vendorError1()<< endl
<< "Vendor error 2:" << aStatus.vendorError2()<< endl
<< "Vendor message 1:" << aStatus.vendorMessage1()<< endl
<< "Vendor message 2: " << aStatus.vendorMessage2() << endl;
}
}
This article was:
Helpful |
Not helpful
Report an issue
Article ID: 877
Last updated: 05 Feb, 2008
Revision: 1
Views: 37680
Posted: 26 Nov, 1997 by
Dean J.
Updated: 05 Feb, 2008 by
Dean J.
Others in this category
Why won't the InfoBrowser contents update in response to selection changes in ClassView or FileView?
Powered by KBPublisher (Knowledge base software)