Database Connection; more robust handling when a database connection is lost

A change has been made to better handle errors when beginning a Database Transaction and the database connection has been lost, e.g. the network has gone down.

Previously a fatal error was generated, meaning all unsaved work is lost. Now, in some forms at least, an error is returned and the unsaved work can be copied to the clipboard, for example.

This is more important for forms involving scripts, and therefore has been implemented in the following Admin forms:

Decision Cards
Documents
Page Sets
Queues
Report Templates
Scripts
Workflow Types

Note, this applies to Microsoft SQL Server databases.