Keep in mind that the webserver is using a login - normally iusr??? or something similar. You will need to give that user rights to where your files are on the other server.

BTW, we did something very similar with a recently released application - it works great.



>Hi all,
>
>The scenario :
>My company distributes a VFP 7.0 application as a tiny executable and all the pieces needed, programs, reports, vcxs, forms, dlls, exes, reports, labels go to our customer’s servers as files contained in subfolders. This way of doing things is very advantageous as when we fix bugs or create enhancements, our support crew just need to connect to the customer’s site and drop small files instead of a whole huge exe or apps. Most of the time, our reps can update our customer’s running application without needing kicking out people from it.
>The disadvantage is that we need to have a good updates file management system in place, but that’s something I finished a while ago and it’s working well.
>Our next step is to have a live update so our customers can pull the pieces and self install them: enter the live update project.
>
>The live update solution :
>I'm finishing a "Live update" feature for this application; it’s written in VFP 8.0, we’ll deploy the VFP 8.0 runtimes, no big deal.
>
>The file management system is complete and at the end of the development of features or bug fixes we have a folder with the updated artifacts (prgs, reports, forms, vcxs, etc) in subfolders in a central server, it includes VSS automation and we have metadata describing and listing them.
>
>My live update concept is simple, the customer will have a “Check for updates” wizard that will use a web method “GetUpdatesList()” in a web service at our company to request a list of updates from their last visit, if there are updates they will be shown and they will pull the updates (all or nothing) using a second web method “GetUpdatesZipFile”.
>This method receives our customer code and the datetime of their last visit, then queries my metadata, obtains a list of the artifacts updated from their last visit, creates a zip file with them and returns the location of the zip file. The wizard will receive the zip file location and the zip file will be downloaded, then deleted from the central location using another web method and then the pieces unzipped and installed on site.
>
>The problem!!!
>I created a class with all the methods described above and it works great, the GetUpdatesList() method produces a XML dataset using XMLAdapter, the GetUpdatesZipFile creates the zip file with the proper files.
>Then I created a dll, tested it, works great again.
>Then I created the web service, tested the GetUpdatesList(), worked great calling it local or from home, this is cool stuff!
>But then, when calling the web method GetUpdatesZipFile(), it does not work!
>The web service lives in a different space (I’m not sure what the buzzword is) and the file system is not available, I’m receiving from my error trapping a message telling me that the files I’m trying to add to the zip file don’t exist.
>So, from the same machine, if I test the GetUpdatesZipFile() method using the class or the dll com object, I’m able to create the zip file, if using it as a web service method, the folders containing the updated files are not visible.
>
>How to make those folders visible/accessable to the web service?
>
>
>TIA