GW> But that is already handled, as name clashes on extract are reported
GW> and if over-write is not allowed extraction is aborted (maybe we should
GW> change things to allow extraction to a modified file name - thoughts   
GW> anyone?).

I didn't like the error handling aborting the extraction so easily, but fixing
that begged a near complete re-write of the extract function, which I wasn't
prepared to do...

I think the extract should be more state-driven than it is rather than being
loop driven... so that it can easily drop an error and get on with the rest of
the script(s)

Bye.
                        

--- EzyQwk V1.20 01fa018d