> > set ftpShellScript to "ftp -d -v -u ftp://" & remoteUserid & ":" & >> remotePassword & "@" & remoteServer & ":21" & remotePath & fileName & " " & >> localFile > > >I should learn to read a bit before posting >(and change my subject lines ;) ). This from 'the man': > >In order to be compliant with RFC 1738, ftp strips the leading "/" from >path, resulting in a transfer relative from the default login directory of >the user. If the / directory is required, use a leading path of "%2F". If >a user's home directory is required (and the remote server supports the >syntax), use a leading path of "%7Euser/". For example, to retrieve >/etc/motd from `localhost' as the user `myname' with the password `mypass', >use "ftp://myname:mypass@localhost/%2fetc/motd" > >It doesn't say what happens if you don't have a leading "/" in your path to >begin with... The path doesn't have to have a leading slash (/), but you certainly need a slash between the host:port and the path in a URL. ftp://user@host:port/ - users home directory ftp://user@host:port/file - file in users home directory (relatively to login directory) ftp://user@host:port//file or ftp://user@host:port/%2Ffile - file in root (/file). ftp://user@host:port/~username or ftp://user@host:port/%7Eusername -username's home directory (although more likely would be an error on many servers). Note that these vary wildly from client to client and server to server. Enjoy, Peter. -- Check out Interarchy 8, just released. <http://www.stairways.com/> <http://download.stairways.com/>