I would like to hear what other VB Database programmers are doing for reasonable
connection strategies within their client applications?

I have begun to employ a connection with Global scope that is opened in the
form open event of the startup form, and is not closed until the application
is terminated.

This is used as the active connection for all ADODB variables and ADO components
where an active connection is required. The benefits are: 1) only one connection
object is registered on SQL Server; 2) if the connection object requires
changes, the changes only need to be amended in one place in the code.

The biggest down side that I can think of is that this approach requires
diligent error checking each time the global connection object is used -
I can't assume the connection is still open.

Any thoughts on this approach?

Regards, Jim