G
Glen Appleton
I posted this earlier with no response, but maybe with some detail I can get
a response this time. :~)-
Situation:
We have a complete failover system in place which means if the main server
(live data) is down you can attach to the backup server (snapshot data).
The backup server data is only current to the previous day's end of
business, but it's adequate for it's purpose.
Scenario:
When the main server goes down, the links in the application to the SQL data
will cause the application to display an SQL server error dialog, and then
prompt the user to enter login information. Both the error and the login
appear to be generic SQL server dialogs. I trap the login error and change
the linked tables over to the backup server to enable continued workflow.
Problem:
The generic SQL error and login dialogs provide information about the SQL
connection that I don't want the user to see. Is it at all possible, at the
application level, to keep these dialogs from appearing and silently
trapping the error? If not at the application level, is it possible at the
user group level on the SQL server to suppress these dialogs? I've searched
google and a great number of web sites, and I can't seem to find an answer
for this.
Any help would be most appreciated.
- Glen
a response this time. :~)-
Situation:
We have a complete failover system in place which means if the main server
(live data) is down you can attach to the backup server (snapshot data).
The backup server data is only current to the previous day's end of
business, but it's adequate for it's purpose.
Scenario:
When the main server goes down, the links in the application to the SQL data
will cause the application to display an SQL server error dialog, and then
prompt the user to enter login information. Both the error and the login
appear to be generic SQL server dialogs. I trap the login error and change
the linked tables over to the backup server to enable continued workflow.
Problem:
The generic SQL error and login dialogs provide information about the SQL
connection that I don't want the user to see. Is it at all possible, at the
application level, to keep these dialogs from appearing and silently
trapping the error? If not at the application level, is it possible at the
user group level on the SQL server to suppress these dialogs? I've searched
google and a great number of web sites, and I can't seem to find an answer
for this.
Any help would be most appreciated.
- Glen