msaccessken
New member
- Local time
- Today, 12:44
- Joined
- Apr 24, 2009
- Messages
- 2
Situation:
Short term, application will be 100% MS Access-contained. Databases sit within the .mdb file. VBA and embedded SQL code will deal with the Jet databases.
Long term, there is a possibility of migration from a fully contained MS Access environment in that the VBA will connect directly to outside data sources, i.e. Oracle or SQL Server.
Before I start developing this app, I want to make sure to minimize potential rework in the future if the longterm plan comes to pass.
1. Do you recommend using the DAO or ADO data access model? If the system migrates as mentioned above, would any DAO code have to be converted to ADO? As I understand it, ADO is much more versatile (or the only way) for connecting to external data sources.
2. If I write SQL embedded in VBA code in an Access module, is this JET SQL or T-SQL? Similar to Question 1, I´m concerned about having to convert JET SQL to T-SQL if the system migrates away from sole-dependency on MS Access and the SQL is being run off of SQL Server or Oracle instead of the internal JET engine.
3. Any essential must-knows/recommendations/pitfalls when beginning development on an application that may need to eventually break out of a fully contained MS Access environment?
Thanks!
Short term, application will be 100% MS Access-contained. Databases sit within the .mdb file. VBA and embedded SQL code will deal with the Jet databases.
Long term, there is a possibility of migration from a fully contained MS Access environment in that the VBA will connect directly to outside data sources, i.e. Oracle or SQL Server.
Before I start developing this app, I want to make sure to minimize potential rework in the future if the longterm plan comes to pass.
1. Do you recommend using the DAO or ADO data access model? If the system migrates as mentioned above, would any DAO code have to be converted to ADO? As I understand it, ADO is much more versatile (or the only way) for connecting to external data sources.
2. If I write SQL embedded in VBA code in an Access module, is this JET SQL or T-SQL? Similar to Question 1, I´m concerned about having to convert JET SQL to T-SQL if the system migrates away from sole-dependency on MS Access and the SQL is being run off of SQL Server or Oracle instead of the internal JET engine.
3. Any essential must-knows/recommendations/pitfalls when beginning development on an application that may need to eventually break out of a fully contained MS Access environment?
Thanks!
