It just dawned on my that in your case you probably don't need to launch and wait, etc but could just wait for the existence of the file:

Sele Fil
Goto top
Do while not eof()
    WZZIP a*.* MyUniqueName      && This is WinZip Command Line
    Copy MyUniqename to Network Drive
    DO WHILE !FILE(networkdrive+'myfile.zip')
       *wait for zip file to exist
       *do whatever to wait probably should include a way out
       *incase the file cannot be created or network drops or 
       *whatever
    ENDDO
    Sele Fil
    SkiP
Enddo

>Hi.
>
>I have an app in VFP which does a call out to the Winzip Command Line to backup some files. Pseudo code as follows:
>
>Sele Fil
>Goto top
>Do while not eof()
> WZZIP a*.* MyUniqueName && This is WinZip Command Line
> Copy MyUniqename to Network Drive
>
> Sele Fil
> SkiP
>Enddo
>
>The problem I have is that control is returned immediately to the Copy caommand, before the Winzip is finished.
>Also, the way Winzip works, the MyUniqueName.zip is actually created on disk at the start of the zip, so I cant test on the existence of the file or not.
>
>I have used a Loop which just waits 1o minutes, but some zips will only take 1 minute and others may take 12 mins.
>
>Any ideas on this appreciated.
>
>regards,
>Gerard