Setting the workflow properties to "Close Connection On Completion" is a
good start. If that isn't working then something must still have hold
of the file. I would use something like Filemon fom sysinternals to see
what grabs the file. I would also try deleting the files outside of the
package as well.

Allan

"Francisco Miranda" <francisco.miranda (AT) gopac (DOT) com.mx> wrote

I've seen this when I've had errors occur in Active X Script task
using the File System Object and I had my error handler simply resume next
Step thru and msgbox out any errors that may occur that you don't see.

You're using the WZip UnZip Command Line Util, right?
Also, how are you unzipping?
Execute Process Task or Active X Script Task? I've had more success with
the latter.

Also, check out ALL the flags that the Command Line Util accepts...one
automatically answers possible questions as 'YES' or 'NO', another closes the
DOS Shell automatically without any prompt...

Are you waiting for WinZip to complete before deleting files?

Hint: I have 2 generic dts packages
a) Zipper (Globals: source, destination, errCode)
b) Unzipper (Globals: source, destination, errCode)

All dts packages call these packages and WAIT for completion before moving
on (ie:deleting files and the like)

ie: Active X Script
pseudo:
for each file in some dir
a) call Unzipper with source destination
b) wait for completion and get errCode
c) next file

Finally, after all our unzipping
Delete the Files (maybe if your looping thru all the Files in a Dir and
deleting them on the fly, the collection is changing...but I'm not sure)
--
later

georgejetson


"Francisco Miranda" wrote: