>If you want to do this, you will want to duplicate the script that the >current button is attached to as it is a nontrivial script that you would >not write by guessing what it needs to do. That is why I recommended just >making the name of the new report the same as the original.
Each report has a script that contains saved automation specific to that report (such as sort, page set up, print, etc.). Not knowing exactly what a user wants to report, I can't recommend that another report's script would be appropriate or not. If a user doesn't know how to read a script or write a new one for his/her report, the FileMaker manual and/or FileMaker consultants are available. Changing the name of an ebase layout not only may not make the script work right, but it'll confuse future users/consultants who try to work with the system. I'd recommend not changing ebase code but rather adding to it. In this case best would be to add a fourth button on the Payments Reports menu and a new script for it to run the new report. Again, document all changes in the ebase file provided. Best wishes, Allen -- L. Allen Poole ebase user support Creative Database Solutions NW 3640 SE 26th Ave. Portland, OR 97202 [EMAIL PROTECTED] (503) 720-3742 ------------------ Reminder to each recipient: To change your list account preferences, go to http://email.sparklist.com/scripts/lyris.pl?enter=support and enter the email address you used to subscribe to the ebase support list:: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] --------------------------------------------------------------------- ebase - Relationship Management for Nonprofits, http://www.ebase.org ---------------------------------------------------------------------
