>Have what generic? The connection pooling? That's a SQL Server thing.

I was looking for a generic Framework.Data.SQLExec() method which I wouldn't have to change if we change the backend. So, what I have now seems to be ok. If I go with the SQL pooling, as you mentioned, it won't work for a VFP backend. However, I could still add a property in the class to initialize something like Framework.Data.lSQLBackend which I could turn to true when I know I will query some SQL Server data. So, with that property on, to SQLExec() method could know how to handle it for SQL Server pooling benefit.