>No, I'm waiting for you all to work out the kinks. ;)

Yesterday it was a funny day. In the middle of the day I got an assignment that involves zipping a file. We already have a case which involves unzipping and we bought command-line interface fo WinZip. So I consulted with my colleague how he implemented this, printed documentation and started experimenting...

First I decided against run command (don't like DOS interface), so I made minor adjustments in my colleague's RunScriptShell function. Then I tried to use the command just by using wzzip zipfile filetoputinzip and it gave an error of file not found. I then did the same using full path to the server. This time I didn't get an error, but the file was not created. Then I tried to do the same from the server itself and it worked. At this point I asked our system administrator to help and he told me, that this probably would not work from another computer, but only from the server.

So I wrote several e-mails and proposed few alternatives. Then I decided to repeat my tests and using Borislav's suggestion of PAUSE command in a batch found that the zip file was updated. So I thought, well, it works after all. I wrote several more e-mails going back to my original question about storing the path to the program. But I was not completely sure, it works. So at night from home I deleted the zip file and re-ran my batch and got an error about not finding some dll and not properly installed add-ins. So, the conclusion - the creating of zip doesn't work, but once the zip is created, it can be updated using command line interface. This brings us back to square one and we again need to choose a zipping mechanism.

Needless to say that I have to write another e-mail after that new discovery <g>

So in a few hours I gone a full circle from hope to despair to hope and back to despair <g>