Does anybody know of a way to limit source codes on the payment screen to only show recent options and hide the ones that aren't currently applicable?
Here are three solutions, from a post by Jack Noll, one of the
designers of version 1.
There are several
ways around this. Remember, value lists can be either custom entries
(you give the list a name and then specify the different values making
up the list) or their values can be drawn from one or two fields in a
file.
The source code value list currently being used when you enter a payment is an example of the latter; it's drawing its values from the records in the solicit_ file.
The easiest way around the problem of getting a huge list is this: Create a new value list in the paymnts_ file named "Short SC List". Type in the specific source codes you want to appear in the list (remembering that, with custom values, you don't get the option of having descriptions that accompany your codes). Then, on the entry layout, attach this new value list to the source code field.
A second option is to export all of your source codes to a new filemaker file named "SCShort_.fp3". This file would only have two fields: the source code and the description. Then, get into that file and delete those source codes that you don't want in your short list. Finally, back in paymnts_, create a new value list called "Short SC List", and have it draw its values from the fields in this new file instead of from the solicit_ file. The benefit here is that you get descriptions. The downside is it's an extra file that you have to open and maintain.
A third way (and I won't get into a step-by-step on this one; you either know what I'm talking about or you shouldn't be doing it) is to create a text field in the solicit_ file named "DisplayInList" and stick it onto the source code entry screen. If the field has a "Y" in it, then you want the record to be in the short list.
Next, create two calc'd text fields: SC4List and SCDesc4List. The calc for the SC4List is:
If (DisplayInList = "Y", Source Code, "")
The calc for SCDesc4List is:
If (DisplayInList = "Y", Source Code Description, "")
Finally, create a new value list in paymnts_ named "Short SC List", and have it draw its values from the these new fields in the solicit_ file. The benefits here are many: you get descriptions, maintenance is easy, the list is totally dynamic, etc. The downside is iyou need to know what you're doing in Filemaker to set it up. This method is basically the answer to your request that we'll probably implement in the next version of ebase.
------------------
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
---------------------------------------------------------------------
The source code value list currently being used when you enter a payment is an example of the latter; it's drawing its values from the records in the solicit_ file.
The easiest way around the problem of getting a huge list is this: Create a new value list in the paymnts_ file named "Short SC List". Type in the specific source codes you want to appear in the list (remembering that, with custom values, you don't get the option of having descriptions that accompany your codes). Then, on the entry layout, attach this new value list to the source code field.
A second option is to export all of your source codes to a new filemaker file named "SCShort_.fp3". This file would only have two fields: the source code and the description. Then, get into that file and delete those source codes that you don't want in your short list. Finally, back in paymnts_, create a new value list called "Short SC List", and have it draw its values from the fields in this new file instead of from the solicit_ file. The benefit here is that you get descriptions. The downside is it's an extra file that you have to open and maintain.
A third way (and I won't get into a step-by-step on this one; you either know what I'm talking about or you shouldn't be doing it) is to create a text field in the solicit_ file named "DisplayInList" and stick it onto the source code entry screen. If the field has a "Y" in it, then you want the record to be in the short list.
Next, create two calc'd text fields: SC4List and SCDesc4List. The calc for the SC4List is:
If (DisplayInList = "Y", Source Code, "")
The calc for SCDesc4List is:
If (DisplayInList = "Y", Source Code Description, "")
Finally, create a new value list in paymnts_ named "Short SC List", and have it draw its values from the these new fields in the solicit_ file. The benefits here are many: you get descriptions, maintenance is easy, the list is totally dynamic, etc. The downside is iyou need to know what you're doing in Filemaker to set it up. This method is basically the answer to your request that we'll probably implement in the next version of ebase.
