Now, we realise what we're looking at is pretty unusual...

The app is using a global database connection which is specified in MSSQLDRV.Int as DAW suggest.

We are looking into the possibility of having the app fail-over to another database on a different database server if the primary one against that app goes down (can't be connected to) regardless of whether it was running when the app was opened or goes down mid-transaction etc.

In a nutshell, we require some automatic way of failing-over the app to a different database server and database should the primary one go down. This is over and above MSSQL Replication functionality.

From memory there is a time-out or something in the driver. But whether we can trap that I am not sure.

Has anyone done anything of this nature before? got ideas???