Thanks Zim, but I really hope that's not the case (or I hope I can find a way to modify my CRecordSet derived class to handle this).

I designed my app with the understanding that it will not always be my project. It may ultimately end up in the hands of someone who does not even know anything about MFC or necessarily C++, so the goal was to design it in such a way that it's highly extensible, flexible, OO, small and reusable. Ideally, adding a new procedure or field or table should only require one extra line of code, not an extra class.
The instructions left for future programmers are like:
"Double-click on XXX function in ZZZ class. Scroll to the bottom of the function and add the line:
m_myObject.AddInformation("yourinformationgoeshere");
replace the part in quotes with the name of your (whatever)."

This model works perfectly right now using a single CRecordSet class to control all database access, when accessing fields and views directly.
My goal however is to take this one step further using stored procedures, so that all the SQL is on the server, thereby increasing performance while making it more of a "thin client" solution where the server has more control over the data, so a hijacked or crashing client going bezerk can't do any real harm by bypassing the protection measures in place on the client side.