(CopyFile ) and (Launch )


[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]

Posted by Robert G Laurin on November 27, 2005 at 18:02:42:

I've been experimenting with the (CopyFile ) mnemonic.

My customers use data export to Excel more and more. I use to have a folder on their Novell server called EXPORT. Unfortunately, as more and more of the users start using the data export facility, we found that sometimes two person tried to access the same exported data file (mostly dot CSV).

So I started experimenting with the Directory Alias in order to drop the exported data file directly into each individual PCs. Because some of the users are in a microsoft domain (aka AD) environment, the actual folder name is a friggen nightmare (see earlier postings in this forum).

So I finally found how to write a program that will work the same for local users and remote users (CometAnywhere). But while testing it I found differences in the behaviour...

The (CopyFile ) Mnemonic will convert the destination file name to all UPPERCASE if copied to a local machine. Remote users keep the MiXeDCaSe as entered.

The (CopyFile ) will accept embedded spaces in the destination file name, but (Launch ) will NOT launch the file if blanks are use on a Remote user (CometAnywhere), it will work fine on a local user.

Consistency would appreciate these two commands to act the same ~ so would I.



Follow Ups:



Post a Followup

Name:
E-Mail:

Subject:

What is the name of the main Signature System's Product?

Comments:

Optional Link URL:
Link Title:
Optional Image URL:

You may attach up to 5 files to your followup (see below):






[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]