Aggravating shortcut!

[JBruyet]

Hey all,

I just loaded Win2K Pro on my computer here at work, but now when I create shortcuts on my desktop to files that are located on the file server I get some aggravating error messages. For example, one file shortcut is named CS BUDGET 2002.XLS. When I click on the shortcut to open the file from my desktop I get three error messages:

1) CS.XLS can't be found
2) BUDGET.XLS can't be found
3) 2002.XLS can't be found

After Excel gives me these error messages it will go ahead and open the file. Is there a way to get Win2K Pro to see the file name as one name without using underscores???

Thanks,

Joe Brouillette

 

[swertel]

Put double quotes around the file name.
"CS BUDGET 2002.xls"

This tells windows to look for the entire string, not words within the string.

Actually, it is best to put the quotes around the entire path in the Target field of your shortcut's properties. The name of the shortcut does not matter.

 

[JBruyet]

The path in the shortcut already has double quotes, and I quote: "H:\Budget\CS budget 2002.xls". I tried using double quotes just around the file name but I get an error message stating that it's an invalid name.

Thanks,

Joe Brouillette

 

[AustinPowers]

Hi Friend,

Instead of H:, try putting the UNC instead....

Yeah, Baby!
AP

 

[Rhonin]

You might also want to check the file association that opens *.xls files.
Under advanced|open|DDE it should read [open("%1&quot].


Rhonin
"too many questions, too little time..."

 

[JBruyet]

AP, The files are on a Novell server and UNC paths won't work with it (I've tried a couple of times with no success).

Rhonin, the file association is exactly as you've listed in your post.

Does anybody else have any suggestions or should I go ahead and use underscores in the file names?

Thanks,

Joe Brouillette

 

[cjhacon]

Are long file names set on the Novell server?

 

[JBruyet]

Yep, long file names are set on the server. My computer seems to be the only one with this problem so I'm thinking it's something in the setup for my workstation but I can't figure out what.

Thanks,

Joe Brouillette

 

[cjhacon]

Went browsing through my Registry Tweaks and Tips (

http://www.pcin.net/help/articles/registry_tips.pdf)

and found the following registry fix.

Stop Win2k/XP from Fixing Broken Shortcuts
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\NoResolveTrack

This DWORD set to 1 will stop Windows 2000 and XP from trying to automatically fix shortcuts. 0 will enable it.

In that you're receiving the three errors it seems that Win2K may be trying autofix.

You could try disabling in registry. You can always enable again if there's no improvement.

Worth a shot!!

 

[JBruyet]

cj,

My registry doesn't have the "NoResolveTrack" key.

Thanks,

Joe Brouillette