>OK, the client was monitoring this discussion with great enthusiasm >hoping for a solution. You are correct, the group of records that needs >an Action will indeed be different every time.
And at various times might be a set of payments, or a set of names records. So the first, manual, steps, would be to find the set of records by what ever criteria apply, and if it is a set of payments, use the transfer to names function to jump to the names file with a found set equal to the names records to apply actions to. There are ebase functions to do this (the Payments and Names query screens, and Transfer to Names) so it's not going to be productive to automate this any more as long as the query will vary. >For example: they are event attendees who have made a payment on a >certain day. Let's say 100 people came to an event on 11/1/2001. I can >generate a group from Payments, now I want to give them all an Action >that they attended Event X, so in the future we can look people up by >their event attendance (or whatever other Action) and not guess from >their Payments records. I really do want to do the same exact thing for >Actions as is available for Contacts. How difficult would it be to copy >and modify the script? Thank you! My first reaction is to suggest you get whoever will be creating this script to track down the scripts that drive the Output Wizard and have a look at them. The process is complex, but not difficult to follow. The problem with simply duplicating the process is that there are several scripts and several layouts involved, and some of the scripts rely on global values set by posting values (e.g., date, type of output, source code) to fields on specific layouts. Certainly possible, but not simple. You could partially automate this by relying on the user to get to a found set in the names file as described above, then manually moving to the Actions file and invoking a script there which would import the record numbers from the names file and jump to a new layout where the script would pause while the user would enter items such as the type of action, source code, and date, then replace the data into the found set. One script, one layout, but a couple of manual steps to be performed by the user. -- -- Dave Shaw H4 Consulting tel: 206-954-7526 fax: 206-625-1338 ------------------ 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 ---------------------------------------------------------------------
