FTPRemoteFileList Problems

Question

I've installed the trial version of edtFTPExpress. I added the FTPRemoteFileList component to a form. Everything works fine for a while. Then, for no apparent reason, when I change directory nothing seems to happen. All I see is a greyed out empty list. None of the files are listed but the headers are there.

If I remove the component and add it to the form again, evereything works, for a while. Then it stops again for no apparent reason.

Answer 1

How long is for a while? The most likely reason is that the FTP server has timed out the connection. The remote file list is tied to the FTP connection so if the connection is broken you'll lose the list.

Answer 2

I'm using VS2008 in debug mode. When I run the project and try to make a connection, I get the problem described. Once the problem occurs, there does not seem to be any other way to stop it except to remove the component from the form and re-add it.

So, the "after a while", is not with respect to the length of time I'm connected to the FTP server. What I mean is, everything works for one or two project runs, but then stops working for no apparent reason. When the problem starts, I trace through my code and everything seems to fire off. I connect to the FTP server just fine (no errors), there are no errors when I call "ChangeWorkingDirectory" either. But nothing displays in the FTPRemoteFileList. When I check the FTP server, it show me connected.

Once the problem starts, the FTPRemoteFileList does not start working again. I have to remove it from the form and re-add it.

Answer 3

I figured out the problem.

I was setting the connction property of the FTPRemoteFileList in the property page not in code. When I set the connection property in code, the problem went away.

Answer 4

It should be OK to set the connection property from the Properties View, unless you have two connections on the form in which case it can sometimes get confused.

Is the directory you're listing very large? Or is the connection perhaps dropping out?

Looking at the log might help figure that out so if it happens again please enable DEBUG level logging and post the appropriate part of the log.

- Hans (EnterpriseDT)