Link to home
Start Free TrialLog in
Avatar of Derek Brown
Derek BrownFlag for United Kingdom of Great Britain and Northern Ireland

asked on

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?
ASKER CERTIFIED SOLUTION
Avatar of Jim Dettman (EE MVE)
Jim Dettman (EE MVE)
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
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.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Derek Brown

ASKER

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
Sorry that should have read Access 2010
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thank you all

Derek
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.