I now understand the wwFTP does not fit this scenario. I'll just have the client use FileZilla to get the files to the server.
Thanks for the additional info.
Hi Robert,
I'm not sure I understand what you're trying to do.
What is running on the client? A foxpro application? Depending on what you're doing cFtpSource will have different meanings (upload/download). Basically if you want to use wwFtp you typically have a FoxPro desktop app talking to an FTP server in the Cloud. The client app uses wwFtp to send the file to the FTP server.
Ftp servers are dumb - they only send and receive files (and a few other things related to file management), but they don't run code. A Web Connection server is not an FTP server, so you'll need to have a separate FTP site in place.
If you need logic behind an upload the way you can do this is:
You can use wwHTTP and set up a custom Process method or Page that handles this incoming HTTP request.
This way you can 'attach' logic to an upload indirectly.
Hope this helps,
+++ Rick ---
Can cFTPsource be a file on the client computer? I want to give site visitors the ability to upload large files (16+ mb) to the WWWC server using FTP. Currently, I get a path error if cFTPsource is set to a file on my hard drive because WWWC tries to find the file on its own hard drive.
