P
Pat Williams
Since .lnk files are blocked, has anyone come up with
a "best practice" of shipping a link to an .exe or an .mdb
to a user, which should be placed on the user's desktop?
I am really beside myself -- it used to be so simple to
just attach a .lnk file to email and send to the user w/
instructions to copy to their desktops. Now, we have to
go through all kinds of gyrations -- I insert a hyperlink
with instructions to have them copy from a folder (which
exposes more than I would like them to see on the network,
plus it's confusing to them), or, I can send them
instructions to copy the line, create a new shortcut on
the desktop, paste into target, etc. etc. This becomes
exponentionally more user-handholding than the earlier
method was, and I am just -- well, it's a huge time-waster
for me. Can anyone shed some light on this? -- Also --
I used to just "rename" the link to .txt and add the
additional instructions that come along with that, but now
you can no longer rename it in a windows environment --
that is, it renames itself to something
like "myprogs.lnk.txt" or ".txt.lnk," I'm not sure. I
have to drop to DOS if I want to do any renaming.
AAAAARRRRR! (and it's a few days after Natl Talk Like a
Pirate Day).
Any help would be appreciated,
thx
Pat
a "best practice" of shipping a link to an .exe or an .mdb
to a user, which should be placed on the user's desktop?
I am really beside myself -- it used to be so simple to
just attach a .lnk file to email and send to the user w/
instructions to copy to their desktops. Now, we have to
go through all kinds of gyrations -- I insert a hyperlink
with instructions to have them copy from a folder (which
exposes more than I would like them to see on the network,
plus it's confusing to them), or, I can send them
instructions to copy the line, create a new shortcut on
the desktop, paste into target, etc. etc. This becomes
exponentionally more user-handholding than the earlier
method was, and I am just -- well, it's a huge time-waster
for me. Can anyone shed some light on this? -- Also --
I used to just "rename" the link to .txt and add the
additional instructions that come along with that, but now
you can no longer rename it in a windows environment --
that is, it renames itself to something
like "myprogs.lnk.txt" or ".txt.lnk," I'm not sure. I
have to drop to DOS if I want to do any renaming.
AAAAARRRRR! (and it's a few days after Natl Talk Like a
Pirate Day).
Any help would be appreciated,
thx
Pat