Application that communicates with a database - how?
-
If you couldn't use MFC integrated database-classes, and you had to create a simple application that communicated with a database, how would you do that? Would you use for instance SOCI, and make your non-GUI classes in STL? I mean, not use CString, but std::string, and when the GUI needs it, convert the std::string to CString and vica-versa? Or would you make all the classes in MFC and add some kind of extra database layer that converts the database-output from SOCI (which then would be a std::string for instance) and make it a CString for your business-object class and then pass that class to the GUI? Please tell if I'm not explaining this well enough.
-
If you couldn't use MFC integrated database-classes, and you had to create a simple application that communicated with a database, how would you do that? Would you use for instance SOCI, and make your non-GUI classes in STL? I mean, not use CString, but std::string, and when the GUI needs it, convert the std::string to CString and vica-versa? Or would you make all the classes in MFC and add some kind of extra database layer that converts the database-output from SOCI (which then would be a std::string for instance) and make it a CString for your business-object class and then pass that class to the GUI? Please tell if I'm not explaining this well enough.
Jan Sommer wrote:
...how would you do that?
I would look here. I would also look to see if the database supported Automation.
"Old age is like a bank account. You withdraw later in life what you have deposited along the way." - Unknown
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
-
Jan Sommer wrote:
...how would you do that?
I would look here. I would also look to see if the database supported Automation.
"Old age is like a bank account. You withdraw later in life what you have deposited along the way." - Unknown
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
Thanks for your reply David I'm looking for something more concrete then ODBC - That's certainly what I'm going to use since the application is going to be cross platform (and the database is an MS SQL Server). But how would you create the classes responsible for holding the database-data which the UI uses?