Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×
The Claris Museum: The Vault of FileMaker Antiquities at Claris Engage 2025! ×

This topic is 5540 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

I am a very recent convert to the changes in FMP that came in with FMP 7. I am working with FMP 9 and I am really struggling with concepts.

I am trying to construct a data base for a non-prof that sterilizes feral cats. They want me to keep track of several types of persons, and what they are doing. As an example:

A person may be a Trapper, a Volunteer, a Donor, or just a person of interest.

I set up a table of Contacts that contains names, addresses, phones, etc. of all persons in any category.

I then set up a table for trappers, and a table for donors. In each of these I assigned an ID number for each of these (Trapper ID and Donor ID) in each table and related them to the Contact ID in the first table.

This works OK, but the ID numbers in each of the three tables have to be the same for each Contact, Donor or Trapper.

I wrote a script, that is executed each time a new Contact is entered, that sets the Donor ID and the Trapper ID to the same number as the Contact ID.

It seems to me that I have taken a difficult approach, and that I should be able to get by on just one ID - but I don't know how to do this, or even if it is possible to do so.

Can anyone help me here?

TIA

Posted

Hi John,

I would approach it differently, ie, all people would be in one table. And then I would either use a multiline checkbox to specify whether they are doner, trapper (or multiple) or I would use a join table.

In this way, you only have one ID because all persons are within the same table. :smile2:

Posted

Hi Laretta

I think you are correct about using Join Tables, however I looked it up in various places and I am somewhat befuddled. Can you point me to a simplified explanation or sample of a Join Table?

Thanks,

John

Posted

Try here .

A multi-line might work for you instead of a join table. I don't know your situation well enough to make that decision but a join table would work well if you need a person can hold many roles and you need to report on the roles (so a person can appear in multiple roles on a summary report). :smile2:

This topic is 5540 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.