Object Dock Plus icons won't open Excel files anymore

from WinCustomize Forums
I've been running OD+ for about a year now without any major problems... until now. For some reason, I can no longer open an Excel file (using either standard or animated shortcuts) from any of my docks. If I click on the shortcut in my tabbed dock, it opens the Excel application, but not the file; if I click in the shortcut in my zoomer dock, I get the same result, and the dock also freezes until I manually open a file from within the Excel window, or just quit the Excel application altogether. Word, Outlook & PPT files still open without a hitch, and I can't remember changing anything. I'm using the very latest (as of 5/19/06) version of OD+ available. Any ideas? Thanks!
objectdock
2,893 views 4 replies
Reply #1 from WinCustomize Forums Top
were the icons set to open specific files?
can't you just redo the link?
Reply #2 from WinCustomize Forums Top
The icon in question has always been set to open a specific Excel file. I've tried to re-link it, but it simply won't open any .xls file at this point. I even added new icons to my docks linked them to new Excel files, and the files simply won't open anymore. I can link to and open all other MS Office files, but no luck with Excel ones. I don't know why.
Groupy 2 - Organize multiple applications into grouped tabs on your Windows desktop
Reply #3 from WinCustomize Forums Top
browse to the excel file and right click on it - in properties make sure the 'open with' asscociation is correct
Reply #4 from WinCustomize Forums Top
Thanks, Sir Bichur. I've discovered that this is a problem with WindowFX 3.0 beta. When WinFX is running, I can't open saved MS Office Excel Workbook files, only the Excel application. If I unload WinFX, the problem goes away. I posted this issue in the support discussion for WinFX, but I messed things up with a multiple post and accidentally deleted all of them! I know, I'm an idiot. Sad thing is, there were 2 replies to my original post, and all I was able to read from the first reply was that someone had confirmed it. That's all I know! Hopefully, someone at Stardock support knows about the issue now.