You'll need a table where each record represents one form being printed for one customer. Your print scripts can create a new record and log the customer and the form being printed. Other fields in this table can auto-enter the date, time, and the account name of the user printing the reportl
Summary reports can then report how many times each report was printed over a specified time range as well as many other variations of this theme.
Ok I get the idea. I have the print log table created. Does it have to be related or is it a stand alone table?
It could be either. IT will depend on how you need to use this data and what data in other tables might be needed for any reporting that you do.
Ok. But if it is unrelated, how do I script it such that it (a) does not visibly switch to another layout and (b) does not create a new record in the incorrect table
I elected to relate it via a filed call Lien ID yet each time I try the script its creating a new "Lien" instead of a new "log entry"
If there are no related records to go to, the GTRR step silently returns an error code and control passes to the next line of your script as though the GTRR step does not exist. See: The Complete Go To Related Record for more on this step.
But you can create a new record with code such as this:
Set Variable [//set variables for any data from the current table that you want to enter in a new record in the unrelated table]
Go to Layout [ Specify layout based on unrelated table here]
Set field [//use set field steps to copy data from variables set at beginning of your script into fields of the new record here]
Go to Layout [Original layout]