This code works beautifully in the element programming:

// Prints the Over 30 Days by Customer report

var vPrintTheReport as String
var vTemp as String
var vFilename as String
var vNewFilename as String
var vPos as Int
var vShell as Int


IF NOT @Mode() = 0
THEN
	{
	vPrintTheReport = @PrintAReport(". Over 30 Days, sorted by Customer", REPORT_MODE_HTML_PREVIEW, PRINT_ORIENTATION_PORTRAIT, 0, -1, -1, -1, -1, -1, -1)
	}
ELSE @MSGBOX("This Report can only be run in Update mode",
		"Please switch to Search/Update and try again",
		"")


// File rename procedure
	// Get just the filename off the full path
	vTemp = @ReplLas(vPrintTheReport, "\", "^")
	vPos = @Instr(vTemp, "^")
	vFilename = @Mid(vTemp, vPos + 1, @Len(vTemp) - vPos)

	// Make the new filename
	vNewFilename = @UserID + "_" + vFilename

	// Issue the rename command
	vShell = @Shell("REN " + @Chr(34) + vPrintTheReport + @Chr(34) + " " + @Chr(34) + vNewFilename + @Chr(34)) 

I've messed around with numerous permutations, but what I started with was putting this in Global code:

SUBROUTINE ChangeReportFilename()
var vPrintTheReport as String
var vTemp as String
var vFilename as String
var vNewFilename as String
var vPos as Int
var vShell as Int

	// Get just the filename off the full path
	vTemp = @ReplLas(vPrintTheReport, "\", "^")
	vPos = @Instr(vTemp, "^")
	vFilename = @Mid(vTemp, vPos + 1, @Len(vTemp) - vPos)

	// Make the new filename
	vNewFilename = @UserID + "_" + vFilename

	// Issue the rename command
	vShell = @Shell("REN " + @Chr(34) + vPrintTheReport + @Chr(34) + " " + @Chr(34) + vNewFilename + @Chr(34))
END SUBROUTINE 

And changing the element code to

// Prints the Over 30 Days by Customer report

var vPrintTheReport as String
var vTemp as String
var vFilename as String
var vNewFilename as String
var vPos as Int
var vShell as Int



IF NOT @Mode() = 0
THEN
	{
	vPrintTheReport = @PrintAReport(". Over 30 Days, sorted by Customer", REPORT_MODE_HTML_PREVIEW, PRINT_ORIENTATION_PORTRAIT, 0, -1, -1, -1, -1, -1, -1)
	}
ELSE @MSGBOX("This Report can only be run in Update mode",
		"Please switch to Search/Update and try again",
		"")


ChangeReportFilename() 

Marvelous, thank you so much.  I knew it was something like that, because I could see that the element programming was creating vPrintTheReport but the subroutine had no way of knowing what it was.  Writeln() tests kept coming up blank.  I had no idea you could pass the info back into the code that way, thanks for teaching me new stuff!!

I would jump at it!  I'm woefully deficient on stuff like subroutines, functions, arrays, result sets, and global values.  Just tell me where and when.

Quote:

Not on me at the moment, sorry. 


In re: the process we've been dealing with above (renaming report files with user names attached) for anyone else considering this who may be reading:  if the user's browser is not open before running the report, it will fail to display when the browser does open, because, of course, the file has been renamed in the meantime and the browser cannot find what it's been told to open.

I'm trying to figure out a way, now, to process the report, rename it, and then display it in the browser.  I'm also considering submitting a feature request to Lantica for a way to automate all this.  Maybe an extra switch added to @PrintAReport allowing one to tag on a value or the contents of an element to a report name?  I can think of lots of uses for this, as the monkey-mass of reports in my Reports folder are just gibberish right now, though some of them could be significant and worth saving for repeated viewing if they were tagged in certain ways.

Version 2.0.6 will make Carl's suggestion a bit easier.

I just added another Mode to @PrintAReport() and @XResultSetPrintReport() that creates the HTML report but does not print it or display it. It just creates it and returns the name of the file. So you can re-name it and display it in your case. or E-mail it, or FTP it automatically or any number of things that you can think of.

-Ray

Ray, about the Mode change you made, if I want to rename the file will I still need to open a shell window?  If not is there, or could there be, a way to manipulate the filename before it is saved to disk (thereby eliminating the shell window)?