Hi, could someone tell me if installing Access Runtime 2010 should be breaking, specifically causing a lengthy repair, of Office 2013 if installed together on the same device?  It seems to be the case but wondering if this should be expected.  Users at our company need a solution for their ADP's until they can be updated but would still like to install Office 2013. 

I'm trying to create an app-v package of the runtime which should solve the problem I'd think if I can create the necessary isolation.   

• Edited by Fed17 Wednesday, July 15, 2015 12:44 AM

Thanks for the reply.  Could you tell me what the reg key HKCR\Access.Application\CurVer is set to on a machine with a working Access Runtime 2010?  Mine without runtime installed is "Access.Application.15" but with runtime installed changed to "Access.Application.14" and then seems to require a repair when you launch the full Access 2013.