365 Backward Compatibility

DB Front End accdb written in 2010 works in 2013. Same DB saved as accde works in 2013. Same DB now opened and edited with 365, saved as accdb works in 2013. Same DB 365 saved as accde will not work with 2010 or 2013. Is this correct?

December 31st, 2014 10:12pm

Hello rpsalty,

Office 365 is not an application, it's a solution (of sort). When you say opened with 365 it's not applicable. What program are you referring to when you say 365?

Free Windows Admin Tool Kit Click here and download it now
January 1st, 2015 8:44am

Hi George,

Oh Im referring to Access. I purchased Office 365, rent I suppose, in lieu of  installing my Office 2010. I was led to believe 365 is Office 2013 that keeps itself updated even to the next upgrade as long as I pay the yearly rent.

Anyway I want to save the database as the executable accde but it wont open with Access in Office 2010 or 2013. It will open using my copy of 365 (Access). If I save the database as accdb, it opens on the 2010 and 2013 installations.

If I use the Access 2010 app on the other computer and save as accde it will open on the Access 2010 and 2013. I can also open with Access 365 solution.

Best regards,

Rob

January 1st, 2015 12:22pm

Hello again,

Yes, this is a bug of some sort. I cannot distribute an .accde to my customers who use Access 2013 Runtime to execute it. I must deliver the original .accdb to make it possible for them to run the code.

It would be nice if MS could step in here and answer this!

Free Windows Admin Tool Kit Click here and download it now
January 1st, 2015 12:49pm

Thanks George,

I'm relieved to know it's not operator error. Perhaps the fix will be in the next update.

Happy New Year,

Rob

January 1st, 2015 12:53pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics