Missing Shortcuts - Filemaker Pro
Not sure where to post this, hopefully this is the right forum. I've been using ZENworks for many years, and the ZEN version of Admin Studio on and off for a few years. Never had an issue quite like this. Driving me crazy. Any advice would be greatly appreciated...
MSI for FileMaker Pro 9 is NOT Taking care of file association.
It shows association , do a right click on an fp7 file, shows Opens with Filemakerpro advance, but when you double click, or do a right click choose open, FileMakerpro does not launch.
When you do "open with" on an fp7 file, FileMaker Pro Advanced is chosen, you click OK, then you get the message, "This action is only valid for products that are installed."
When you choose a file with the extention fp5, everything works well with no issues.
I have manually changed the file associations in Windows, making a snap shot of the changes, looked at each registry key, and tried to manually add the registry keys to the MSI. No Luck.
I have tried numerous ways to add the registry keys involved here, and no luck.
This makes no sense. FP5 files work fine, FP7 files do not, even thought the FP7 files have the FP icon associated to them, they act like the application is not installed.
This one really has me stumped. Is there something unique about FileMaker Pro 9? Is there something unique about FP7 files?
MSI for FileMaker Pro 9 is NOT Taking care of file association.
It shows association , do a right click on an fp7 file, shows Opens with Filemakerpro advance, but when you double click, or do a right click choose open, FileMakerpro does not launch.
When you do "open with" on an fp7 file, FileMaker Pro Advanced is chosen, you click OK, then you get the message, "This action is only valid for products that are installed."
When you choose a file with the extention fp5, everything works well with no issues.
I have manually changed the file associations in Windows, making a snap shot of the changes, looked at each registry key, and tried to manually add the registry keys to the MSI. No Luck.
I have tried numerous ways to add the registry keys involved here, and no luck.
This makes no sense. FP5 files work fine, FP7 files do not, even thought the FP7 files have the FP icon associated to them, they act like the application is not installed.
This one really has me stumped. Is there something unique about FileMaker Pro 9? Is there something unique about FP7 files?
0 Comments
[ + ] Show comments
Answers (8)
Please log in to answer
Posted by:
tmiller
16 years ago
My organization runs just an older 5.5 version of FileMaker. I have rebuilt it and run in to pretty much the same problem as you. On mine I don't have .fp7 associations due to the older version I am using, but I can not get it to accept my .fp5 associations. I get the same thing you are talking about where the icon shows up for the files but if you look at what program is associated with it, it doesn't know what to use.
Not really helpful but would like to also hear if anyone else has a solution to this.
Not really helpful but would like to also hear if anyone else has a solution to this.
Posted by:
HabMan
16 years ago
tmiller,
Just wonder, have you packaged many Apps? The newest version of ZEN Admin Studio, v 8.x, has been great. Much better that previous versions. This is the first issue with an app that I have not be able to somehow solve or repackage.
Been to the Filemaker Pro Knownledge Base, but have yet to find much helpful there.
To any of the experienced App packaging folks out there... If you could enlighten me a bit ...
I read Addressing Problems with File Assocations http://itninja.com/blog/view/autoexnt1
Could someone please elaborate on this comment ...
To generate advertising information you should add the file association in the file properties within your MSI editor (GUI). Do not add the file associations from the registry directly (if you want the advertising information included).
Exactly where do I add the file association in the MSI editor?
And if someone could further elaborate on " Do not add the file associations from the registry directly (if you want the advertising information included)" I'm not following... Why?
Thanks!
Just wonder, have you packaged many Apps? The newest version of ZEN Admin Studio, v 8.x, has been great. Much better that previous versions. This is the first issue with an app that I have not be able to somehow solve or repackage.
Been to the Filemaker Pro Knownledge Base, but have yet to find much helpful there.
To any of the experienced App packaging folks out there... If you could enlighten me a bit ...
I read Addressing Problems with File Assocations http://itninja.com/blog/view/autoexnt1
Could someone please elaborate on this comment ...
To generate advertising information you should add the file association in the file properties within your MSI editor (GUI). Do not add the file associations from the registry directly (if you want the advertising information included).
Exactly where do I add the file association in the MSI editor?
And if someone could further elaborate on " Do not add the file associations from the registry directly (if you want the advertising information included)" I'm not following... Why?
Thanks!
Posted by:
tmiller
16 years ago
Hey again, Sorry it took so long to reply. I thought I would get an email when anyone replied. Oh well.
As of this afternoon I have done 38 various rebuilds and tune ups on programs.
I understand sort of what you are saying on the file associations. It makes sense that you may not be able to push the association by editing the registry direct.
I just now stumbled upon something maybe useful. There is a way to use a command line to change associations. It might be easiest to build your package without the association, and then run an included .bat file that will add the association for you. I am going to attempt this in a bit. I will post back if I have any luck.
Thanks!
As of this afternoon I have done 38 various rebuilds and tune ups on programs.
I understand sort of what you are saying on the file associations. It makes sense that you may not be able to push the association by editing the registry direct.
I just now stumbled upon something maybe useful. There is a way to use a command line to change associations. It might be easiest to build your package without the association, and then run an included .bat file that will add the association for you. I am going to attempt this in a bit. I will post back if I have any luck.
Thanks!
Posted by:
anonymous_9363
16 years ago
ORIGINAL: tmillerUse the 'Subscribe' link: it's at the top of this page, about 1/3rd of the way down on the right.
Hey again, Sorry it took so long to reply. I thought I would get an email when anyone replied. Oh well.
Posted by:
tmiller
16 years ago
Oh ok!!! Done! Thanks VBScab!
After attempting this a little more. It seems like my .msi gets the correct file association for .fp5. The files get the correct icon and know to open up using FIleMaker. Also, using "Assoc" from a command line, the computer has the right association. My problem seems to be more that the call to the program does not function for some reason. When I double click a file, nothing happens at all.
After attempting this a little more. It seems like my .msi gets the correct file association for .fp5. The files get the correct icon and know to open up using FIleMaker. Also, using "Assoc" from a command line, the computer has the right association. My problem seems to be more that the call to the program does not function for some reason. When I double click a file, nothing happens at all.
Posted by:
anonymous_9363
16 years ago
As ever, use ProcMon to watch what the app is doing, file- and registry-wise. It's just guess-work otherwise.
Posted by:
HabMan
16 years ago
It might be easiest to build your package without the association, and then run an included .bat file that will add the association for you.
I know there are work arounds on the back side to change things than an MSI did, and scripts to correct "mistakes" but my question regarding this is two fold.
1) Are issues like this just the nature of application packaging? Guess I'm scratching my head why, when using the vendor's original install msi with a simple mst, I should even have issues like this.
2) Trying to understand how to incorporate changes in a standard install, or simple "fixes" into an mst, so additional scripting after the install is not needed.
Posted by:
HabMan
16 years ago
Could someone please elaborate on this comment ...
To generate advertising information you should add the file association in the file properties within your MSI editor (GUI). Do not add the file associations from the registry directly (if you want the advertising information included).
Exactly where do I add the file association in the MSI editor?
And if someone could further elaborate on " Do not add the file associations from the registry directly (if you want the advertising information included)" I'm not following... Why?
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.