Reputation: 176
We have an Access database we built in Access 2003 that is pretty simple, just a bunch of tables, forms and reports that work in tandem for data entry. We want to repurpose the objects in that database and build a new db in Access 2010, to finally get with the times.
Note, we do not need to upgrade or convert the old database (with all of the existing data). But want to start fresh and create a new database in 2010 that functions just like the old one.
I have tried two methods and they give me different results, I am hoping to get some insight as to why: ONE: First, I opened my newly installed Access 2010 app and pointed to a copy of my old .mdb. Opened it and did a "Save Database as" .accdb with a new name. Access thought for awhile then told me "This Database has been upgraded..." Opened the database via my Main Menu like a user would, but the basic functionality of my new database doesn't work. The debugger gets prompted on my first or second button event click. So I think, "Guess I have to rewrite my VBA!"
TWO: I opened a empty database in Access 2010. Then imported all of the objects right from my old .mdb (tables, forms, queries, macros, modules, reports, blah blah). Opened the new .accdb database via my Main Menu and every button, every field on every form worked like a charm.
Can anyone tell me what Access did during that "upgrade?" If option two worked for me, am I golden without having to do major recoding (once I have finished rigorous testing that is)?
Thanks in advance!
Upvotes: 0
Views: 2017
Reputation: 176
Looks like I found a fix. My Access 2003 database was running a legacy version of ActiveX Data Object Library (2.1). I think that when Access 2010 did the upgrade, this reference library was too old to operate with 2010. Simply unchecking this library (View Code-->Tools-->References) or updating to ActiveX Data Objects 2.8 restored full functionality of my forms.
This link talks about legacy ActiveX Data Objects. http://support.microsoft.com/KB/825440
Upvotes: 0