Mike McCracken
asked on
Convert MS Access 2000/2003 db/application to Access 2010
I have been asked to convert an Access 2003 db/application to Access 2010 (may be able to stay at 2007)
What issues can I expect?
Will the tables convert cleanly and it is only the code that may cause issues?
I haven't seen the database as of yet. I believe it is relatively small with minimal code and just a few tables.
mlmcc
What issues can I expect?
Will the tables convert cleanly and it is only the code that may cause issues?
I haven't seen the database as of yet. I believe it is relatively small with minimal code and just a few tables.
mlmcc
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I know about the accdb vs mdb issue.
I haven't seen the database yet so I amnot sure what all it has. A potential client has asked my company for help. Apparently they tried to upgrade to 2007 (not sure if it was just open in Access 2007 and run or to an accdb) and apparently they had some issues.
We have been asked to give them an estimate of the effort involved and I just am trying to anticipate if there will be any real issue. I know I ran a fairly complex (lots of code and screens) database as an mdb for a long time before we changed it over to accdb.
I don't recall any real issues occurring while it was an mdb. I don't recall if it was originally a 2003 app or if it was built in 2007. I took it over when they wanted to use 2007.
thanks
mlmcc
I haven't seen the database yet so I amnot sure what all it has. A potential client has asked my company for help. Apparently they tried to upgrade to 2007 (not sure if it was just open in Access 2007 and run or to an accdb) and apparently they had some issues.
We have been asked to give them an estimate of the effort involved and I just am trying to anticipate if there will be any real issue. I know I ran a fairly complex (lots of code and screens) database as an mdb for a long time before we changed it over to accdb.
I don't recall any real issues occurring while it was an mdb. I don't recall if it was originally a 2003 app or if it was built in 2007. I took it over when they wanted to use 2007.
thanks
mlmcc
..ok, great, then it looks like Kelvin has you covered...
ASKER
Thanks. I didn't want to say 10 hours when there is a good chance it is 100 or 100 when it is most likely an easy task.
I'll ask for more information after seeing the database and when I have more information on it.
mlmcc
I'll ask for more information after seeing the database and when I have more information on it.
mlmcc
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Yes,...Please continue with the experts here who are working on your direct issue here.
I was just wondering about the number of fields.
You can post another question about that later...
;-)
Jeff
I was just wondering about the number of fields.
You can post another question about that later...
;-)
Jeff
ASKER
They want to upgrade to ACCDB format but find that some of the features they are used to have changed.
For instance
They open a table
They right click a data element and see the empty filter box.
In the ACCDB the box isn't there but other options they don't understand are presented.
If they leave the database in MDB format are the right click options the same as they were in Access 2003 or do they change to 2007/2010 menus?
They have a bunch of macros to do the data manipulations they need for doing the payroll.
For instance one they mentioned clears a table and imports the payroll data for the last 2 weeks.
Are macros like that affected by the upgrade to 2007/2010?
mlmcc
For instance
They open a table
They right click a data element and see the empty filter box.
In the ACCDB the box isn't there but other options they don't understand are presented.
If they leave the database in MDB format are the right click options the same as they were in Access 2003 or do they change to 2007/2010 menus?
They have a bunch of macros to do the data manipulations they need for doing the payroll.
For instance one they mentioned clears a table and imports the payroll data for the last 2 weeks.
Are macros like that affected by the upgrade to 2007/2010?
mlmcc
Yes, the new features will be present regardless of the format. I'm working with an older 2000 file, and when I open a local/linked table in Datasheet view I see the same interface I do when working with an .accdb file.
Many of those features have been revamped. For example, the Search features you will find in a Table datasheet view are (IMO) much more robust. If you rightclick on a field, you'll see a menu selection named "Text Filters" which gives you quite a few options for searching the contents of the column. There are also frequently used filters, like "Does Not Equal xxxx" (where "xxx" is the value in the selected box). All in all, MSFT did a pretty good job of providing more user functionality in views like this.
Like everything else, the new UI is one they'll have to get comfortable with.
Many of those features have been revamped. For example, the Search features you will find in a Table datasheet view are (IMO) much more robust. If you rightclick on a field, you'll see a menu selection named "Text Filters" which gives you quite a few options for searching the contents of the column. There are also frequently used filters, like "Does Not Equal xxxx" (where "xxx" is the value in the selected box). All in all, MSFT did a pretty good job of providing more user functionality in views like this.
Like everything else, the new UI is one they'll have to get comfortable with.
Are macros like that affected by the upgrade to 2007/2010?Generally speaking macros which do nothing but manipulate data have no troubles. Macros that call out to VBA functions could run into the same issues you would find with VBA code (i.e. the OpenReport issue, or the ! vs . issue).
Hey nice to see you in the Access zone...
;-)
To be clear are you actually converting to the .accdb format, of just upgrading Access?
Just note that after you convert to the .accdb format, you may not be able to convert back to the .mdb format.
So unless you need a feature specific to the .accdb format you can always keep the db in the .mdb format for a while... (until all users have acc 07 or higher installed)
;-)
JeffCoachman