Access 2010. I have a program that has worked perfectly for over a year in Access 2007. Callbacks, ribbons, all work as they should. I just moved the program from 2007 to 2010 and now the callbacks don't work at all. The only difference I can see is that Microsoft Office Object 12.0 is loaded for Access 2007 and Object 14.0 for 2010. There is no way to load object 12.0 in Access 2010 that I can see.

The error message?: Microsoft Access cannot run the macro or callback function 'onRibbonLoad'.

Is there some way to convert/make a ribbon developed in 2007 work in 2010? Is there some other reference I should be using?

Thanks again! (IMG:style_emoticons/default/thanks.gif)

I have only seen a few small differences in ribbons between 2007 and 2010, some of the imageMSo names have changed which image it maps to (for example).

I have not seen any ribbons stop working depending on which version of Access is used.

Of course the ribbons I usually use might not be that complex, I tend to just have mostly buttons on the ribbon

I would take a look for you if needed.

Probably need more info. See website if you want to email.

Mark Andrews
RPT Software
http://www.rptsoftware.com

I must be slipping. I thought I posted my findings, but I don't see them here.

Thank you for your response:

However, I found the problem, after several days and many hours of struggle. Simple. The Access 2007 version I created the original project with was a 32 bit version, even though running on a 64 bit OS. The Access 2010 version I now run on is a 64 bit version. There are several compatibility issues between the 32 bit Access and the 64 bit Access. (That took many hours to find out, shouldn't have, but evidently no one on this forum knew either, so I don't feel too badly).

I had to create a new blank 2010 64 bit Access database. After creation I copied and pasted from the 32 bit project into the 64 bit. I then went in and set my declare statements to ptrSafe and made a couple of simple tweaks after that, and everything worked fine and is working great at this point.

Thanks again for the response.

Glad you figured it out. Note: most people just force the client to use the 32 bit version of Access 2010. You can run 32 bit version of Office 2010 on win7 64 bit operating system for example.

Mark

However, in this instance the client needs to connect to multiple databases as desired. My understanding, and theirs, is that this cannot be done with 32 bit, but only with 64.

Maybe "yes", maybe "no".