🚀 go-pugleaf

In article <gexhtUO00iV1E4hmQ0@andrew.cmu.edu>, David Tsai <dt1n+@andrew.cmu.edu> writes:
> 
> Hello again.  
> 
> Has anyone tried to use the "report" command on page 162 language refernce?
> 
> report ([CPU];""} is supposed to allow the user to generate their own
> report in runtime just like the quickreport at the user level.  When I
> tried to implement this command, all I got was the dialog box to open a
> file.  So I created a report using quickreport and saved it.  And then
> ran my custom report procedure again, and it doesn't even show the saved
> quickreport file that I had just made.  
> Unless someone can prove otherwise, I think that this command doesn't do
> what anything...let alone what it is supposed to!
> Does anyone know what I can do to get it working?  Or should I just give it up?
> 
Dave,
	To open the quick report editor you need to suply a file name that does not
exist. I usually do this:

Report([FileName];"DoesNotExists")

As I understand it, if you submit a empty string (i.e. "") an open file dialog
box is displayed to allow you to open a previously save report, it a file
name is actually entered then it will print a report using that quick report 
layout, and finally if a filename is entered that does not exists the editor
is displayed.

Peter