Chuck,
For debugging...

One thing I've tried is adding code to both cConnectionManager.UnregisterSQLConnection() as well as cConnectionManager.RegisterSQLConnection(), making it output - via STRTOFILE() - useful information. This would include the current alias, the connection #, and # of current references to that connection. In the end, you may end up with quite a file, but some useful information about how the connections are being managed, as well as which ones the manager "thinks" are still left available.

---J

>Thanks Jason,
>
>Your reply help tremendously. I'll keep searching...
>
>Thanks,
>
>Chuck