Jim,

One other option to consider, rather than using AddObject() would be to use a Collection property on the ODBCManager class, this would give you the benefit of having all of the DataManagers collected into one thing that can be iterated. This would also be handier if the ODBCManager class can aggregate other classes as well, the Objects[] collection can be iterated, but you'd need to check the class to see if you had a DataManager as opposed to some other contained object.

>Hey, cool idea with the oODBCManager.AddDataManager() method. I'll look into going down that path. What I'm doing is creating a class for business objects that I can instantiate for each table in my system as I need them. So when I start a form I can call out the ones necessary. oPrimeKeys is one that I was thinking I'd probably keep as long as the oDBCManager object is alive since it would be used frequently. My intention is to release the data manager objects when a form or formset terminates and they are no longer needed. I want to register them with the oODBCManager so that they will be released regardless when the that object is killed.