Title: Re: [support] How do I enter complimentary memberships?
Ali,
You can enter a payment of $0 and make a note in the Payment For memo line. If you need even more ways to find them you could add a category to the Member type field for complimentaries. Also, if these people/organizations gave some in-kind donation you probably want to figure out the dollar amount and add another payment record with the same date as the $0 dues record and enter that amount as a contribution. That way they are tracked as a member and as a contributor--full value for the money!
--
Beth Hynes
Parks & Trails Council of Minnesota
26 E Exchange St #100
Saint Paul MN 55101
[EMAIL PROTECTED]
651-281-0508

We've just finished a huge event and would like to give a few complimentary memberships to donors of the event.  Since dues info is tied to payment info, what do most people do?  Do you enter a false amount like $1 or something?
Thanks!
 
ali
 
Ali Duvall Jonkel
Five Valleys Land Trust
PO Box 8953
Missoula, MT  59807
(406) 549-0755
[EMAIL PROTECTED]
-----Original Message-----
From: Dave Shaw [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 21, 2001 7:50 AM
To: TechRocks Support
Subject: [support] Re: How do I order the source code drop-down list?

Hi all:
Maybe I'm missing something.  I've created various source codes.  Ebase
seems to order the source codes alphabetically according to their
descriptions.  I'd like to change the order but can't seem to figure out
how.  Edit, cut, paste, etc work on other drop down lists but don't seem to
work on the Source Code list.  Any ideas?  Thank you.

You're not missing anything. The source code list is not a standard "custom values" value list, but is drawn from a field in the solicit_.102 file. This presents all the values in the field, sorted alpha, and you get nothing to say about it.

Jack Noll published some workarounds a while back. His solutions are at the bottom of the message.

By the way, I appreciated an answer a while back that also referenced a page
number in the administor's manual.  I find the advice offered by this group
helpful, but I also appreciate the reference to where to look so that I can
help myself.

Good words, and I agree. Manual reference allows people to follow up later or extend the answer on their own. This case, however, is off the map. It's not a built-in ebase solution, so is not documented.

---------------------------
Jack's solution:

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.
--
--
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
---------------------------------------------------------------------
------------------
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
---------------------------------------------------------------------

------------------
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
---------------------------------------------------------------------

Reply via email to