[support] Re: multiple organizations-one database or more

[Cecily Clemons]

Title: Re: [support] Re: multiple organizations-one database or more

here's a less technical answer to your question....I would definitely separate all the organizations in terms of donations etc....  Donations are confidential information to each organization and to share information like this is, well, at the risk of sounding dramatic, a bit unethical.  Think about it from the donor's perspective:  they give to your organization and trust that you won't share that information with other organizations, who could use it to their advantage.  As a fundraiser, going from organization to organization, I am ethically bound to the organization I worked for....so, if a donor contributes to organization 1 (where I used to work) and to organization 2 (where I currently work), I am bound to not divulge the information I learned from working at organization 1.

So, I'd say, get 3 copies of ebase, one for each organization.

-Cecily


--
Cecily Clemons
Development Director
Predator Conservation Alliance
[EMAIL PROTECTED]g
406.587.3389
406.587.3178 (fax)

Saving a place for America's predators

Looking for the perfect gift?
Support our conservation work and give a gift you can feel good about.
http://www.predatorconservation.org/merchandise.html

From: Allen Poole <[EMAIL PROTECTED]>
Reply-To: "TechRocks Support" <[EMAIL PROTECTED]>
Date: Mon, 18 Feb 2002 16:13:33 +0800
To: "TechRocks Support" <[EMAIL PROTECTED]>
Subject: [support] Re: multiple organizations-one database or more

>We'd planned to keep all three
>lists in one database, assuming that it would be easier to maintain just one
>database. That's true when we're talking about  mailing lists. However, now
>that we're beginning to track dollars, I'm not so sure.  Anybody have any
>experience using ebase to manage development projects for more than one
>group?

I've addressed a similar issue for small business (operating as more
than one company with a common staff) by building custom systems that
keep client/vendor/contacts in a common list but segregate all
invoices, payments, receipts, etc. by company.

ebase has no built-in way to do this, and it'd be a significant
amount of work to customize either version to make it separate
solicitations/payments/items by to-whom-they-pertain.

I can think of some far-fetched tricks to try, but without having
tested them I won't even mention them!

If you don't have significant FileMaker development resources, I'd
say you should keep three copies of ebase.  If it's helpful, you can
synchronize the names files to cut down on data entry redundancy.

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

------------------ 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:: archive@jab.org To unsubscribe send a blank email to [EMAIL PROTECTED] --------------------------------------------------------------------- ebase - Relationship Management for Nonprofits, http://www.ebase.org ---------------------------------------------------------------------