'Where in my VI would this reside, inside or outside any loops.'
All depends on what you're trying to do and what kind of program architecture you're using (multiple loops, state machine, events, etc?). I'll make some assumptions and say put the code inside a case structure inside one of your loops. Tie the case structure to logic for whatever it is you want to trigger the creation of the files (boolean button, time of day, etc.)
Attached is really rudimentary demo of Print VI to HTML VI method in LV6.1.
If you haven't already done so, check out the LV examples. "Print LLB to HTML Custom.vi" is pretty close to this.
Side issue:
If you want to know what an error code means/is, right click on the code number in the error c
luster (which you should be religiously using). At the top of the popup menu that appears is 'Explain Error' which when selected will give a little explanation about the error. Error 7 for LabVIEW is 'File not found'.
I easily got Error 7 by deleting the directory c:\HTML test and then running the code in my previous post. Code was telling it to store files there and LV is replying that it's not there.
=====================================================
Fading out. " ... J. Arthur Rank on gong."