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 6780 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

small annoying problem this time guys, hope you can help...

ive got a list of contacts where some entries are family and the others are just friends. ive got all the details, such as name, adress, and phone for each contact. what i want now is a checkboxfield below the contact info called "family?" were you check "yes" for familymembers, or "no" (or just leave blank) for others. the thing is that i want this connected to a table which creats a new entry for every family member and sticks them inte the table (this all because it going to be easier to send mail to them all, yes im just that shallow and unpersonal :))

now, i know how to script a button to do all this, the thing is that i think i looks better with the checkboxes. is this possible? did anybody get what im trying to do?

Posted

I'm not sure you really need another table for this information. Just having the checkbox for family gives you a field to perform a find request on family members, then run your mail script on the found set.

Posted

no, i need the table, gives me a good view of my familycontacts... the thing is that im planning on doing the samething for work, and other contactgroups aswell, and them im gonna need the diffrent table anyhow...

Posted

Here's one idea:

Leave your checkbox where it is on the layout, but change it to a button to perform a Toggle script such as:

If [Table::Field = "Yes"]

Set Field [Table::Field; "No"]

Else

Set Field [Table::Field; "Yes"]

Perform Script

End If

This example assumes the checkbox field is Text and you would, of course, have to confirm that the family records don't already exist from a previous toggle operation. The displayed checkbox will update appropriately upon each toggle.

Posted

Since you want to consider Family as a category (a subset of contacts) I would reflect this in the relational strucure rather than applying the logic externally after the fact with a query. Splitting Family into a new table is not a good idea in my opinion.

Keep them in the same table. Create a new stored calc text field 'cYes'. the calculation would be :)

"Yes"

Make a new Table occcurence of your Contacts Table, called 'Family' and relate

contacts::cYes = Family::Checkbox

now you can display them through a Family portal, gather them all with a GTRR step, create valuelists based only on Family, etc...as well as include them in a mailing to all contacts without having to duplicate your process for a different table.

-Raz

Posted

thanks K1200, this is sort of what i wanted...

now i only need to make sure there is no dubbles, and besides i also need it to remove the contact from the list if i check "No", had i by misstake checked the wrong person...

This topic is 6780 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.