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