We help IT Professionals succeed at work.

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

Derek Brown
Derek Brown asked
on
231 Views
Last Modified: 2014-12-22
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?
Comment
Watch Question

President / Owner
CERTIFIED EXPERT
Fellow
Most Valuable Expert 2017
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION
Jim Dettman (EE MVE)President / Owner
CERTIFIED EXPERT
Fellow
Most Valuable Expert 2017

Commented:
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.
CERTIFIED EXPERT
Distinguished Expert 2017
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION

Author

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

Author

Commented:
Sorry that should have read Access 2010
Dale FyeOwner, Dev-Soln LLC
CERTIFIED EXPERT
Most Valuable Expert 2014
Top Expert 2010
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION

Author

Commented:
Thank you all

Derek
CERTIFIED EXPERT
Most Valuable Expert 2014

Commented:
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.
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.