Are there any problems converting an Access 2002 MDB to Access 13?

I need a fresh look for my app.

Are there any problems converting an Access 2002 MDB to Access 13?
Can an app developed in 2013 be distributed with the relevant runtime (if it is still called that) without braking any rules?
Derek BrownMDAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
The answer is, as it often is, "it depends".   A2013 depreciated a number of features, such as ADP's, Command Bars, dbf support (see https://support.office.com/en-us/article/Discontinued-features-and-modified-functionality-in-Access-2013-bc006fc3-5b48-499e-8c7d-9a2dfef68e2f?ui=en-US&rs=en-US&ad=US)

 If you don't use any of those, then no, there is no major changes except that A2013 is also the first version where you must live with the ribbon.

 Unlike 2010 and prior, which honored your menu bars, 2013 will not.  Instead it places them on a tab in the ribbon.    That more that anything you will have to deal with.

Also, if you convert to the the ACE format, you loose work group security.  Again not a biggie if you were not using it, o a major pain if you were as you will need to replace it.

Jim.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
BTW, from A2010 up, the other thing to watch out for is that Office comes in both 32 and 64 bit editions.

If you use no 3rd party controls, use Windows API calls, ODBC drivers, and distribute not as a MDE/ACCDE, then no problems.

If any of those are true, then you need to be aware of the differences.

 and note that 32 bit Office runs under 64 bit OS's; you don't need to use 64 bit under a 64 bit OS (In fact Microsoft is still  recommending 32 bit for the majority of users).  So the simplest thing to do is avoid 64 bit installs if you can.

Jim.
0
PatHartmanCommented:
The Access runtime used to be very expensive but as of A2007, MS has been offering it as a free download.  Just be aware that installing an app on a computer that has just the Access runtime will result in security messages.  To make them go away permanently, you would need to update their registry to add the proper keys.  If this is an in-house app, your systems administrator can "push" the correct registry keys so you don't have to manually do it on each computer.  If the app is for external distribution or you don't have any way to push registry keys, then the simplest solution (although not cheap) is to purchase an installer such as SageKey which will handle installing the FE, BE, runtime, and registry keys along with anything else you need installed.
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Derek BrownMDAuthor Commented:
Thank you both.

Can I run Access 2002 as well as 2019 on the same machine that I use for designing and developing access applications?

Derek
0
Derek BrownMDAuthor Commented:
Sorry that should have read Access 2010
0
Dale FyeCommented:
If you want to do that, I would recommend doing it in a Virtual Machine, so that each of your versions of Office exist on different virtual machine.  This will prevent version conflicts from occurring.
0
Derek BrownMDAuthor Commented:
Thank you all

Derek
0
Nick67Commented:
One other possible gotcha.
Access 2002 was the only version that had ADO as it's default library.
All others before and since had DAO as the default library.

Nothing may break out of the box, but switching the order of the libraries, or failing to preface all DAO items with syntax like DAO.Recordset may lead to unexpected results.  The recordsets of all objects like forms and reports are created with the highest priority library leading to forms and reports based on ADO recordsets.

With the ADO library as higher in priority than DAO, the RecordsetClone object does not have a .Bookmarkable property, for example.  Be aware that such oddities may occur, and don't let them stump you, and you will likely be okay.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.