I've asked alot of questions and received a lot of help, so in some small
attempt to return the favor, I will mention that I was able to establish a
set of related "Notes" files for each of our users which only they can open
with a password. These files are related to the ebase database, so that a
user can query the ebase database for a record number and then enter that
number into their "ConfiNotes" file (which then pulls the name from ebase)
and then make their own confidential notes for that record. (Among other
things, the staff users determine suitable "matches" for mentors and
mentees)
"ConfiNotes:username" uses a customized variation of the ebase "Notes"
template. Of course, users can make "public" notes on a record as well
within ebase, but the private notes never get shared. These files are
hosted on the server along with the ebase files, so backups are automatic
via FM Server and not left to the discretion of each user.
By doing this, I was able to overcome the aspect that EVERY networked user
would have access to ALL information for all the records in ebase (even the
ones they are not "responsible" for). In effect, this gives me a degree of
"record-level" security for the confidential stuff pertaining to records,
while still keeping the other stuff networked and accessible. (I didn't try
doing this with layouts and "groups" because that would affect ALL records
equally).
I don't know if this is a novel approach, but if anyone's interested, I can
provide more details.
Thanks for all the help folks!
Colin
