>What's the purpose again of the NAME option in the REPORT FORM command? I've looked in the help file, but it's chinese to me.
>
>I am asking because I've come across a strange bug. If I omit the NAME clause, my formset is closed before the report is generated. If I add the NAME clause, my formset stay alive. For example:

REPORT FORM IA200000 TO FILE c:\temp\temp.ps NOCONSOLE   && The formset is closed
>REPORT FORM IA200000 TO FILE c:\temp\temp.ps NOCONSOLE NAME whatever   && The formset stay alive

Anyone know why the NAME clause is mandatory for my formset to stay alive?
>

Here's what we said in HackFox:

Last, but by no means least, is the NAME clause. Although reports and labels are not objects (in the OOP sense), their data environments are. The NAME clause lets you assign a name to the DataEnvironment of a report or label. You can use that name in method code (which seems like a bad idea to us—use This instead) or from the Command Window or a program; with the NOWAIT clause of PREVIEW, your program can still be running while the preview is displayed. You can also reference the data environment from code running in the entry and exit events for the report's bands. We haven't ever actually used these abilities in an application, but it's nice to know they're there. By the way, if you don't include the NAME clause, you can still reference the data environment by using the report name.

Tamar