Hi,

I try to create a very simple FTP get job, but have a problem
with local download folder.

I log in to ftp server, to remote folder /aaa
download to local folder \bbb but VC seems
to insist om local folder to be \bbb\aaa , e.g. appending
remote folder to local download path...?

Is this by design?

Svein

Hi Svein,

1. which version are you using right now?
2. could you give us the exact local and remote folder so we can test it here?

---

This is version 5.5.0 and I tried with several paths and folders and it seems to be the same result.

I have a MS ftp server, log in to folder /nada

I want to download content to:

C:\test

and get the result error finding path c:\test\nada\filename.ext


If i create the folder C:\test\nada it will dowload just fine.

svein

ok, we need to know the exact source path as well to determine if there is anything special with the given path. I am talking about the absolute path - not the relative.

---

This is the absolute path, and is the home dir for the user NADA on the
ftp server,and the path is given as / in VC.


svein

I am not sure if we misunderstand each other.

Let say you have a folder called download in the users home folder. Then you should specify the following in VisualCron

/nada/download

If you want to download from you home dir you should specify:

/nada

---

No, we do not misunderstand, and you are right,
if i specify /nada it works just fine.

But the ftp server is set up with drop folders
that let users just log in and upload directly
in the dir they log in to. If I do the same in VC
, enter just / the ftp explorer will put me in the
right remote folder, and also the ftp task will
download the file from the homefolder (/nada). So why
VC would want to modify the local path is a mystery
to me, but not a problem as long as i know the workaround.

;-)

svein

The reason is that VisualCron know very little about internal folders. The way it is built know we require a reference to the absolute folder. We are thinking about other ways to handle this but this is considered a "safe" way for us to determine and calculate destination folders as well as traversing sub folders.

---