We have several programs in our organization with various levels of affiliation who all currently have FileMaker databases.� Our central administration has gone to FileMaker/ebase 102 and now the question is whether to incorporate the program databases into the central one.� The conventional wisdom among ebase users/trainer seems to be that one database per organization is best and, I agree that there could be lots of wasted opportunity and/or duplicated effort if, for instance, one program has info on an activist's interests that other programs don't have access to. But there are potential problems.� We don't� want all the affiliated programs to have access to giving history information to the central organization.� Is there a way to block access to this information?� Any other suggestions? Thank you- Helen Head -- Please reply to [EMAIL PROTECTED], and NOT to the verizon.net address in the From: field! �
begin:vcard n:Head;Helen tel;fax:(802) 863-2532 tel;work:(802) 863-2345 x-mozilla-html:FALSE adr:;;;;;; version:2.1 email;internet:[EMAIL PROTECTED] fn:Helen Head end:vcard
------------------ 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 ---------------------------------------------------------------------
