Posted January 11, 201213 yr Not sure how this has gone completely unnoticed. But, if it has been noticed, I haven't found it anywhere. I spent the better part of the day tracking down a problem in which ACCESSDE.DLL still builds the /12.0/ hive into the Trusted Locations key when building a deployment package. I patched the thing myself but one might have thought that the resulting application constantly requesting authority to run built-in automation would have been caught by QA. HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Access\Security\Trusted Locations\ Should be: HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Access\Security\Trusted Locations Just in case anyone else cares, this will make the resultant application appropriately "trusted" on launch. In the binary, ACCESSDE.DLL: Offset 0x443E should be 0x34 (Ascii value for "4") Continue reading...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.