What are some important considerations that should be taken into account when upgrading DAO technology to ADO?
You must analyze two possible scenarios: DAO with Data Binding. You must make some manual changes in the upgraded code because DAO data binding is not supported in Visual Basic .NET. Code that uses DAO at run time is upgraded correctly by the upgrade wizard; it uses a wrapper to the DAO library, but you must manually recode all of the data control code if you want to maintain the data binding in your project. The best strategy is to replace your data control with an ADO Data Control before you upgrade your project to Visual Basic .NET. DAO without Data Binding. When an application like this is upgraded to Visual Basic .NET, the upgrade wizard adds DAO library a wrapper to the new project. As a result, code that uses DAO data objects does not require manual changes, and the behavior is the same as it is in Visual Basic 6.0.
Related Questions
- Are there special considerations I need to take into account when using the eFluorTM Nanocrystal conjugated antibodies for flow cytometry?
- What are some important considerations that should be taken into account when upgrading DAO technology to ADO?
- What design considerations does the builder need to take into account to accommodate a Solar Hot Water system?
