This is a really big question: How do you design a VFP program so that it is easy to change what data store it uses?
I'd like to design a new program I'm working on so that it normally uses DBF's, but can be switched to use SqlServer, MSDE or MySql as a back end.
I think many may jump at the quick answer "Use views in a DBC"... but I don't think that's a complete answer:
1) What do you have to do to a view to adjust it from accessing DBF's to accessing MySQL or SqlServer?
2) How do you manage using SQLEXEC for running SQL UPDATE and INSERT commands where, I think, the syntax differs from one DBMS to another?
3) How do you deal with the different Type identifiers in CREATE TABLE commands?
Another "quick answer" many might want to say is "Use business objects"... however, that just avoids the question...: How do you design business objects that handle the above issues?
I'm sure I'll come up with more questions along this line as I work on this... thanks everyone for considering it!
I'd like to design a new program I'm working on so that it normally uses DBF's, but can be switched to use SqlServer, MSDE or MySql as a back end.
I think many may jump at the quick answer "Use views in a DBC"... but I don't think that's a complete answer:
1) What do you have to do to a view to adjust it from accessing DBF's to accessing MySQL or SqlServer?
2) How do you manage using SQLEXEC for running SQL UPDATE and INSERT commands where, I think, the syntax differs from one DBMS to another?
3) How do you deal with the different Type identifiers in CREATE TABLE commands?
Another "quick answer" many might want to say is "Use business objects"... however, that just avoids the question...: How do you design business objects that handle the above issues?
I'm sure I'll come up with more questions along this line as I work on this... thanks everyone for considering it!