locked
Access Versions RRS feed

  • Question

  • I have used various versions of Access over the years.  I have been using Access 2013 since it was released. 

    I am contemplating purchase of a new computer that would have Office Pro 2019 on it.  My question is, if I develop/edit existing applications using Access 2019, will I be able to save them to use with older versions of Access?

    Most of my clients are using Access 2010 or 2013, but some are using older versions.

    I have been able to support these older versions developing on my Access 2013 machine, but that is a windows 7 machine, and I should probably upgrade windows.

    • Edited by tkosel Monday, June 22, 2020 8:59 PM
    Monday, June 22, 2020 8:55 PM

All replies

  • Most of my clients are using Access 2010 or 2013, but some are using older versions.

    Hi tkosel,

    Access is not backward compatible, but is upward. So for development you need to take the oldest version of any of your clients, This is more or less independant of the Windows version.

    Personaly, I am still developing in A2003, with no problems with the higher Access versions. Recently the last A2003 turned over to A2007, and I can change to A2007 as development version.

    Imb.

    Monday, June 22, 2020 9:17 PM
  • As usual, thanks for your timely and informative response.  However, I do not completely understand.  I have been using Access 2013 for many years.  It gives me the ability to save the db in the format for several versions of Access.

    This has seemed to work for me just fine.  Wanting to know if I will be able to do that with Access 2019.  Perhaps I should use my version of office 2013 on my new windows 10 machine?

    Monday, June 22, 2020 9:29 PM
  • As long as you use only features that were available in Access 2010, and only the standard references in Tools > References... in the Visual Basic Editor, it should work if you develop in Access 2019.

    But for example if you set a reference to the Word or Excel object library, it will probably cause problems if the database is opened in an older version.


    Regards, Hans Vogelaar (https://www.eileenslounge.com)

    Monday, June 22, 2020 9:47 PM
  • Thanks as usual for your input. 

    So, bottom line, should I convert the existing older version access .mdb files to .accdb files?  I don't even know what is available in access 2019, but just speculating.  I understand  the reference issues, but do not usually use references to other office application object libraries in my applications, so should be OK.

    Monday, June 22, 2020 9:58 PM
  • Also,

    If I need to create a new application for a customer who has older versions of Access, will I be able to use Access 2019 to save it in the desired format like I was able to do with Access 2013?

    Monday, June 22, 2020 10:15 PM
  • Using a newer version to write apps for users on older versions is asking for trouble. Don't do it.

    It can be references (which you say you don't use) but it can be a simple small feature in form design that is not supported in older versions, and then you'll be back here asking why the <beep> your code does not work for them.

    Compiling to accde (you do compile, right?) and then running on an older version can also cause problems.

    If every customer is on A2010 or better as you stated, you should convert to accdb, to stay current and potentially use new features. Do your development in 2010.


    -Tom. Microsoft Access MVP

    Tuesday, June 23, 2020 12:37 AM
  • The Golden rule of development (Access at least) is to do all development using the oldest version that will be used to run the database.  So if you have clients running 2010, 2013, ... Then you, as the developer, should be using 2010.  Using anything else is asking for trouble.

    As others have stated, Access is backwards compatible, but not forwards compatible (no software is!).


    Daniel Pineault, 2010-2019 Microsoft MVP
    Professional Support: http://www.cardaconsultants.com
    MS Access Tips and Code Samples: http://www.devhut.net

    Tuesday, June 23, 2020 1:46 AM