>Ok, I want to spread teh risk in a backup procedure. I have usually 3 NT4w's networked together. I am using Dynazip to make the archive.
>
>I want to reference another machine's drive, and I cannot assume that there is a map establised. This will be delivered to thousands of installed locations in the next year.
>
>*-- my file list
>ThisForm.Dzocx11.ItemList = "\vitech\data\*.*"
>*-- Test on use of my laptop
>lczipfilename="\\SCR_LAPTOP\$c\Store0"+lcStore+'-';
> +left(cmonth(date()),3)+alltrim(str(day(date())))+right(str(year(date())),2)
>
>ThisForm.Dzocx11.ZIPFile = lczipfilename
>
>I get the error back from dynazip that I cannot make the file.
>
>What am I missing.
>

The odds are that you do jot have the necessary permissions on the target machine. If you are not running in a domain, and you log into alocal system, that does not authenticate you on other systems - you have to explicitly force a login on each system. If no explicit login attempt is made to the other system, the local account and password are passed, and if eachmachine has a different setof users/password sets, no tickee, no washee.

You need to operate in a domain, and make people log into the domain, to get cross-system authentication to work. Logging into a local account doesn't cut it. A good general practice is to force a login to the system by attaching the shared resource to an unspecified local device using WNetAddConnection3() and trapping any failure before referencing the UNC.

Second, if you're trying to access the default hidden C$ share, it's C$, not $C, and only local administrators have automatic access rights granted to \\machinename\C$, so it's a bad idea IAC.

Third, I'm not sure, but I don't rememeber that DynaZip would create new folders if they did not exist. You'd best check to see the folder exists...