When you have Access 2003 and 2007 you get a very long ‘Configuring’ message when you open them alternatively.

This is not good, but I can live with it as a developer.

It really impacts our customers, when we give them a runtime in 2003, and they use Access 2007. Those customers are getting this message all day long.

Figure: This long message is caused only because they launched the Microsoft Access 2003 runtime prior

Figure: If they exit Access 2007, then they open the Access 2003 runtime app, the penalty is the long message again

When you have an Access 2003 Runtime installed (only) + using Office 2007, Windows Updates recommends (aka gives end users grief) patching Word 2003 etc (which they don’t even have).

PS: Times like this I wish Access was not tied in with Office.

Currently, it opens the last version of Access that was opened! This is not a solution.

It gets worse when the user has Access 2007 installed + Access 2003 Runtime version. After using the runtime, double clicking on an .MDB makes it try to open a 2007 version in 2003.

When you delete a reference it actually doesn’t release the reference. You can see the reference is still there when you loop through the references in VBA.

The problem is Access crashes happen after this (this is not consistent and we are fairly sure this is the issue).

When the user moves the location of the commandbar (aka Toolbar), the location is not saved when in runtime mode.

This is a bug.

Note: Access 2007 solves this by using a ribbon and the user cannot move them