DLL Hell, Click to Run office 365 wont run basic functions from an office 2016 .ACCDE

%3CLINGO-SUB%20id%3D%22lingo-sub-1187579%22%20slang%3D%22en-US%22%3EDLL%20Hell%2C%20Click%20to%20Run%20office%20365%20wont%20run%20basic%20functions%20from%20an%20office%202016%20.ACCDE%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1187579%22%20slang%3D%22en-US%22%3E%3CP%3EClient%20Verison%3A%2016.0.12430.20264%20Office%20365%20CTR%2032BIT%3C%2FP%3E%3CP%3EMy%20Version%3A%2016.0.4266.1001%20Office%202016%2032%20BIT%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20I%20deploy%20the%20.accdr%20basic%20string%20functions%20fail%20hinting%20to%20me%20there%20are%20DLL%20versioning%20problems%20somewhere.%26nbsp%3B%20What%20can%20I%20do%3F%20I've%20been%20developing%20with%20access%20for%20a%20decade%20plus%20and%20this%20sort%20of%20thing%20has%20happened%20about%204%20times%20in%20my%20career%20and%20its%20very%20frustrating%20that%20a%20major%20version%20conflicts%20with%20another%20major%20version%2C%20my%20installer%20deploys%20the%20RTE%20and%20the%20.accdr%2C%20obviously%20on%20a%20click%20to%20run%20365%20client%20the%20RTE%20doesn't%20install%20because%20its%20not%20required%20but%20I%20dont%20understand%20why%20this%20basic%20basic%20conflict.%26nbsp%3B%20As%20a%20sanity%20check%20I%20installed%20the%202013%20RTE%20so%20i%20could%20run%20it%20side%20by%20side%20with%20the%20click%20to%20run%20365%20(Microsoft%20Access%202013%20-%20Build%3A15.0.4569%20Run-time)%20and%20still%20same%20problems%20%3A(%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22DLLERROR.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F172551i464B3B242C7B1106%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22DLLERROR.png%22%20alt%3D%22DLLERROR.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%E2%80%83%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1187579%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAccess%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
New Contributor

Client Verison: 16.0.12430.20264 Office 365 CTR 32BIT

My Version: 16.0.4266.1001 Office 2016 32 BIT

 

When I deploy the .accdr basic string functions fail hinting to me there are DLL versioning problems somewhere.  What can I do? I've been developing with access for a decade plus and this sort of thing has happened about 4 times in my career and its very frustrating that a major version conflicts with another major version, my installer deploys the RTE and the .accdr, obviously on a click to run 365 client the RTE doesn't install because its not required but I dont understand why this basic basic conflict.  As a sanity check I installed the 2013 RTE so i could run it side by side with the click to run 365 (Microsoft Access 2013 - Build:15.0.4569 Run-time) and still same problems :(

 

DLLERROR.png