I've created an app in Access 2013 (using a .mdb file) with a custom ribbon and it works OK. When I open it in Access 2007 the app also works, but my custom ribbon is not displayed. Instead, it displays the default from Access 2007. What should I change in order to hide the default one and show my own?
THNX
CodePudding user response:
Going forward in Excel, or PDFs or Access or whatever? Works well for the last 25 years of the computer industry.
but, going backwards? Hum, that's a challenge.
So, for example, you can't take software running on windows 10, and say run it on a older windows 3.1 computer. So, how the computer industry works? Should not be a surprise to anyone with knowledge of or having used computers for more then say a few years.
Think of going backwards and trying to run windows software on a older DOS computer. It will not work - too many updates and changed occurred. However, for a VERY long time, those newer computers - even today windows computers allowed you to run that older DOS software.
if you going to develop an access applcation that is to run and work for access 2007 (now a whopping 15 years old!, then you have to develop in that version. As noted, a access 2007 application should run fine - even with access/office 2019 (or whatever the latest version is).
You could check the ribbon define.
So, say this:
<customUI xmlns="http://schemas.microsoft.com/office/2006/01/customui">
<ribbon startFromScratch="false">
<tabs>
.etc .etc .etc
So, in above, we see office 2006, and that ribbon would thus work for access 2007.
However, for 2010 (and later, while the above would work, you could check the schema setting, and you tend to see say this:
<customUI xmlns="http://schemas.microsoft.com/office/2009/07/customui">
So, check the ribbon schema setting - moving back to the above 2006, it may well work correctly - worth a try.
However, access received a BOATLOAD of new features in version 2010, and if those features were used, they don't exist in 2007 version.
CodePudding user response:
All you've mentioned is understood, but the reason a 2007 version is still deployed, is because customers don't want to change it. Unfortunate, but true. I'll try to create a 2007 ribbon xml as part of the ribbons table and see how it goes.