Linked Table manager in Access2010 runtime

SeadogMariner
SeadogMariner used Ask the Experts™
on
I've created a custom ribbon that makes the Linked Table Manager available to the end-user in runtime mode.
 
When clicked in the XP runtime mode, error reads:  
"The wizard you've requested is not installed or is in a bad state.  Please install or reinstall the wizard.  If you do not have permission to do this on your computer, please contact your help desk representative."

The Linked Table Manager works fine on the development computer (Windows7 64bit, Access2010 32bit) when called using target:

"C:\Program Files (x86)\Microsoft Office\Office14\MSACCESS.EXE" "F:\MyFolder\FE.accdb" /runtime

Are there some additional files that need to be packaged in the setup files (using INNO) to allow the Linked Table Manager to work in runtime mode?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database Architect / Application Developer
Top Expert 2007

Commented:
I'm thinking the LTM is simply not part of the Runtime ... But, with that target ... you are emulating RT, right?

It's possible that there is a difference between that and the actual RT.

mx
SeadogMarinerManaging Partner

Author

Commented:
Correct- the target path forces the RT environment on the development machine.

I'm guessing from what I have trouble-shot so far that your first statement is correct, however I am looking for confirmation to this thesis.

In the meantime, I just found a very slick substitute at JStreet Technology called JStreet Access Relinker.  Took all of about 10 minutes to import a couple of macros and modules, compile, and reconstitute the MS LTM button on the ribbon to call the macro.  It checks for linked tables and opens WinExplorer to give the user the option to link elsewhere.  Real Cool.
Linked Table Manager works fine in runtime emulation.  I haven't used the actual runtime, so I don't know for sure.

Are you sure F:\myfolder is a trusted location? If you remove the /runtime switch does the database work as expected?
Acronis in Gartner 2019 MQ for datacenter backup

It is an honor to be featured in Gartner 2019 Magic Quadrant for Datacenter Backup and Recovery Solutions. Gartner’s MQ sets a high standard and earning a place on their grid is a great affirmation that Acronis is delivering on our mission to protect all data, apps, and systems.

DatabaseMX (Joe Anderson - Microsoft Access MVP)Database Architect / Application Developer
Top Expert 2007

Commented:
Armen Stein's Linker is cool.  And I suspect he would have popped into this Q and offered it. I've met him at the MVP summit and he is a pretty sharp guy.

mx
Thanks MX!  Yes I would have!

Glad you found it, seadogmariner.

Cheers,
Armen
SeadogMarinerManaging Partner

Author

Commented:
Thanks MX and thank you Armen for a slick tool.  

For peter57r, yes the F:\MyFolder is a trusted location (actually C:\Program Files\MyFolder), the registry changes are handled thru Inno set-up adding key to HKEY_CURRENT_USER\software\microsoft\office\14.0\Access\Security\Trusted Locations\MyKey.  And yes, the db works fine in the actual RT with or without the RT switch.  Everything works as expected with the exception of the LTM.  I should also mention that I created two seperate means to call the LTM.  The first was to add the LTM button to a custom ribbon.  Clicking the button in XP RT only version gives the error msg mentioned above. The second was a form button added to the splash screen using the click event: DoCmd.RunCommand acCmdLinkedTableManager.  Nothing happens on the XP RT version when the button is clicked.

As per my research thus far, I am going to assume that I have determined that the LTM is non-functional in the actual RT (only) version. I can only assume that this might be why Armen took the time to create his nice alternative.

Again- thanks all.
Well, we originally created it because the LTM is so annoying and complicated, especially for apps with more than one back-end database.  And ours also has more features like the silent auto relinking to databases in the app folder.  We just don't use LTM for anything anymore, especially not to inflict on our end users!  :)
SeadogMarinerManaging Partner

Author

Commented:
Hello ArmenStein:
Just one more quick question... can your linker be used with a passworded Back-End database?

Thanks again.
Hi SeadogMariner,

The J Street Access Relinker does not currently work with password protected back-end databases.  It could probably be adapted to do so, but we haven't had the need to do it yet.  One complication is that it would need to store a list of known databases and passwords, or prompt for passwords, which is additional complexity that isn't needed for the current version.

Anyone is welcome to enhance the Relinker code and continue to use it, provided that you leave the J Street comments intact.

Cheers,
Armen Stein

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial