> How do we change the name on individual contact records and/or notes?
> Can we change the name easily on the contact record for a "batched"
> message, or must we do each record separately?
The added by and modified by fields are not on any layouts. You have to have
FMPro; get into layout mode; and add them to any layout that has other
fields that has other fields that you can use in find requests to find the
ones you want to change. Then use FMPreplace script to replace them.
>
> > >
> >> On a related matter, I'd thought it was possible to vary access to
> >> some files on a user by user basis. Does that mean that each separate
> >> user must have different machines to make this work?
>
>
> And an added question regarding passwords. Can we alter the password
> itself while retaining the same privileges and can we assign a
> variation of the password to different users.
>
> For example, there are two people who should have "master" level
> access. Can we assign one the personal password "masterone" and the
> other the personal password "mastertwo?"
>
The FileMaker protection mechanisms are fundamentally flawed (my opinion),
at least partially because of differences between what is available in the
OS on Macs vs PCs.
There are both user and group password schemes. eBase uses only the group
features. These are slightly weird in that there is not a userid and
separate password associated with each group. The group name ***is*** the
password. There are scripts on the Admin2 screen for changing the group
passwords. These should be used since the passwords are really on each file.
The admin scripts know how to change the password on all the files. If you
don't use the scripts you have to change the password on each file
individually. The guest passwords are screwed up as no one every set a
password for all the files in the distribution. If you want to add a new
group, mastertwo, you will either have to modify the scripts or visit each
file. The user based passwords are even more cumbersom.
Disclaimer: the above info is based on reading and playing around the edges
of the problem, not actually doing it.
