Hi Rick,

I wrote myself a little unzipping utility a while back based on the help examples. There's no rocket science involved with this code besides yours. 😃 Basically I pass it a text file with a list of zips to unpack, and the destination to unpack to. I read the file into an array and then iterate. The bit that does the work code looks like this:

@ 3,5 SAY [Started at ]+TTOC(DATETIME())
FOR m.lnI=1 TO m.lnZIPs
	@ 5,5 
	@ 5,5 SAY [Unzipping ]+JUSTFNAME(m.laZIPs[m.lnI])+[ into ]+ADDBS(JUSTPATH(m.laZIPs[m.lnI]))+JUSTSTEM(m.laZIPs[m.lnI])
	@ 6,5 SAY [Working...]
	IF m.loZip.unzipfolder(m.laZIPs[m.lnI],ADDBS(JUSTPATH(m.laZIPs[m.lnI]))+JUSTSTEM(m.laZIPs[m.lnI]))
		@ 6,5
		@ 6,5 SAY [Done]
	ELSE
		@ 6,5
		@ 6,5 SAY [Something went wrong]
		@ 7,5 SAY m.loZip.cerrormsg 
	ENDIF 
NEXT
@ 8,5 SAY [Finished at ]+TTOC(DATETIME())

I was demoing this to my team today and it kept failing. The error returned is:

Type is not loaded. Please make sure you call LoadAssembly first.

I swear this was working for me but not sure if the last time I used it successfully was prior to the 8.5 release. Is there some way you can tell from this what's causing my issue? Perhaps a mismatched DLL?

TIA

Once again, the act of writing the message leads to the solution. The folder I was demo unpacking into had old WW libraries.

In the immortal words of Emily Litella, "Never mind."

Wow @ syntax. Now there's something I haven't seen in... 30 years 😄

What would you do in VFP? Write a markdown file and invoke MM? I know. You wouldn't write it in VFP. 😃

We have a photo export function that can generate quite a few zip files as time-limited (3 days) downloadable links generated via a queue read by an async external .Net app which was written by my web dev. My poor customers then have to click each link in the email to download the zips, then unpack them in whatever way works for them. I threw together a couple of quick & simple prototypes intended for me to use in my dev environment; one does the downloads, and the other does the unzipping. Ultimately I plan on baking this into our app and as always you've provided the toolkit to handle the plumbing.

Not @?

If you're doing console style output, just ? operations I guess or Wait Windows.

+++ Rick ---

For these little tools I want to show the start, stop, and processing per file in the same place. I don't really need to see the history for each file downloaded or unzipped. Hence the venerable @..SAY stuff. It's a little more entertaining with the download tool as that echoes X of Y bytes for each file as it is downloaded. Another approach I've taken for this kind of stuff if I need more detail or want it to persist is to build a string, write to a file, then modify file at the end.