none
Backward compatibility between Access 2010 and Access 2007 RRS feed

  • Question

  • Hi,
    I'm developing an application in Access 2010, but need to run it in Access 2007.
    When using Access 2007 I change all the required dll references to work in 2007,
    When I open it in Access 2007 the application runs fine just with two issues:
    1 - A warning bar with a message appears and have to close the warning bar in clicking the X

    2 - When i try to Compact and Repair Database in 2007 I get this message:

    Can someone help me with this, I'vd check everthing and can't find the source of the problem

    Thanks

    João


    Joao Simplicio Rodrigues

    Thursday, September 22, 2016 3:21 PM

All replies

  • Hi,

    It's considered "best practice" to develop in the lowest version you need for functionality because newer versions can run them If you can do a C&R in 2007, it means you can develop in 2007, so I would recommend you just use 2007 and both your 2007 and 2010 users will be able to run the application without any problems. Otherwise, you can try exporting all objects into a brand new 2007 database until the error goes away. However, it won't guarantee the complete application will work after you remove the problem. You may have to replace it using 2007.

    Just my 2 cents...

    Thursday, September 22, 2016 4:19 PM
  • You are not talking about backwards compatibility, but rather forwards compatibility.  You are expecting the older version to be able to support what is created in a newer version of the same software.  This is simply unrealistic.  No software is forward compatible.  It may happen that it will work, but 99% of the time changes made to software break it since the features do not actually exist in the older version that were exploited in the newer version.

    When developing, you always develop using the lowest/oldest common denominator.  In this case, you as the developer, need to do your development using Access 2007.  It will then be able to automatically run on both 2007 and 2010.  The inverse, as you have found out, is simply not a guarantee (or likely).

    Switch to 2007 and everything will fall into place for you.


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

    Thursday, September 22, 2016 11:30 PM
  • Hi,

    Your comments obviously make perfect sense and I didn't observed these principles because of the mine particular circumstances.
    My question is related to the messages.

    My application works well in O2007 the problem are the messages.
    I have revue all the VBA References to all dll, and the messages still show up.
    What I'm looking for is a clue to something I missed.
    Regarding the title of the post is not original, I was inspired here:

    Backward compatibility between Access 2010 and Access 2007

    Thanks anyway.

    João


    Joao Simplicio Rodrigues


    Monday, September 26, 2016 5:50 PM
  • It is doubtful it is something you have missed.  It is more likely a new bit of information that 2010 embeds into it's files that 2007 doesn't and isn't chokes on.

    I myself have seen that error a while back and the only solution was to use a VM with the older version of Access.  Then I created a blank 2007 accdb and imported everything.


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


    Monday, September 26, 2016 5:58 PM