FileMaker supports two forms of protection, groups and individuals. Ebase
uses only the groups which do not allow that fine grain control as currently
structured. Using individual control would be even more work. Perhaps
Version 2 will structure the protection differently.
> -----Original Message-----
> From: Kim Dixon [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 20, 2001 7:39 PM
> To: TechRocks Support
> Subject: [support] Payments protection
>
>
> I now have several of my co-workers who need to use ebase. I'm afraid of
> them accidentally deleting or changes payment information.
> However, I want
> them to be able to use the notes function of the system. Is there a way I
> can make the payments information read only? None of the password
> information describes this type of security.
>
> ------------------
> 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
---------------------------------------------------------------------
