I am a church musician (and definitely not a computer professional) that us=
es a FileMaker for a repository of worship planning information (hymns, ant=
hems, scriptures, sermon title, etc. etc.). There are probably 40 different=
 fields in the database, with a different record of reach Sunday of the yea=
r. It is password protected, and is published to the web via Filepro web sh=
aring on our server (with dedicated IP address).=20

I want to make available to choir members the music coming up for the next =
six weeks. So I created a read-only second database, WITHOUT a password, fo=
r choir members to click and see what is coming for the next six weeks. Eac=
h of the 12 fields in this second database pulls the data from the master d=
atabase. I do not want to give out the password the main WORSHIP PLANNING d=
atabase to my choir; I only want to provide them with one-click link to un-=
editable information. I've found (novice that I am) that this second, non-p=
assword databased requires that the user enter a password for the master da=
tabase before it will pull the data into the second read-only data base. Is=
 there an easy way to make this second database available to my folks witho=
ut giving out the password to the master database? Or (more likely) is ther=
e a completely different approach that would accomplish what I want? Many t=
hanks for any ideas.

In article <674b6943-065c-4072-a529-84f7580c534d@googlegroups.com>,
 kwjazzer <ken@knollwood.org> wrote:

> I am a church musician (and definitely not a computer professional) that uses 
> a FileMaker for a repository of worship planning information (hymns, anthems, 
> scriptures, sermon title, etc. etc.). There are probably 40 different fields 
> in the database, with a different record of reach Sunday of the year. It is 
> password protected, and is published to the web via Filepro web sharing on 
> our server (with dedicated IP address). 
> 
> I want to make available to choir members the music coming up for the next 
> six weeks. So I created a read-only second database, WITHOUT a password, for 
> choir members to click and see what is coming for the next six weeks. Each of 
> the 12 fields in this second database pulls the data from the master 
> database. I do not want to give out the password the main WORSHIP PLANNING 
> database to my choir; I only want to provide them with one-click link to 
> un-editable information. I've found (novice that I am) that this second, 
> non-password databased requires that the user enter a password for the master 
> database before it will pull the data into the second read-only data base. Is 
> there an easy way to make this second database available to my folks without 
> giving out the password to the master database? Or (more likely) is there a 
> completely different approach that would accomplish what I want? Many thanks 
> for any ideas.

Stick to the main database. Create a new user account that is read-only, 
that has no password. Then your choir members can use that to look 
things up, but not change anything.

You could create a new layout that only shows the fields you want the 
choir members to see, and set it up so that that layout is the one 
displayed on the web view.


All that can be doe in the one main database.

I'll do that; thanks so much.