Jump to content

Search the Community

Showing results for tags 'many-to-many'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type

Community Forums

  • The New Claris Platform
    • FileMaker Pro 19
    • FileMaker Server 19
    • FileMaker Server 19 (Linux)
    • Claris Connect
    • Core ML
    • NFC and iBeacons
    • Add-on Modules
    • iOS Shortcuts and FMGo
    • Save Schema as XML and Upgrade Tool
    • Java Script and the Web Viewer
  • Community Resources
    • Community Articles, Tips, & Techniques
    • FileMaker Marketplace Discussions
  • FileMaker Platform
    • FileMaker Interface Features
    • FileMaker Schema & Logical Functions
    • FileMaker Go for iPad and iPhone
    • FileMaker and the Internet
    • FileMaker Pro 18 Advanced
  • FileMaker Server Administration
    • Previous Version Server Discussions
    • FileMaker Cloud
    • FileMaker Custom SSL Certificates
    • oAuth and External Server Authentication
    • Zabbix Server Monitoring
  • Brain Food
  • FMForums Affiliates & Sponsors
  • FileMaker Classifieds
  • FM Forums Operations
  • FileMaker Friday Night Chat's Topics


There are no results to display.

There are no results to display.


  • White Papers
  • Infographics
  • Samples
  • Add-ons
  • FMGo
  • Solutions
  • Tutorials
  • Plug-Ins

Product Groups

  • Workplace Innovation Platform
  • Site Advertising
  • Development & Hosting

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start







Website URL




OS Version

Found 6 results

  1. Hi, i am stuck for a few days creating an many-to-many relation and view/edit it via a portal, which shows the many-to-many. for a better understanding i attached a screenshot of the relationship graph. in the "Personen" table there will be basic informations of all persons (Name, LastName, Birthday, etc.) a person could be an Employeee (Mitarbeiter) with additional informations, stored in the "Mitarbeiter" table. (RoomNumber, OfficeNumber, etc.) a person can also be be a child. if an employee have a child (or more), the basic data for the child is saved in the "Personen" table and with the many-to-many relation the "Mitarbeiter.ID" will be mapped to the "Personen.ID" in the "Kinder" table. so now i would like to have an layout, where i can add an Employee. first it is necassary to enter the basic informations of the employee (Name, Birthday, ..) to the "Personen" table. after that the "Mitarbeiter" table should be filled with work-related data (OfficeNumber, ...). after the employee basic data is entered and he has an "Mitarbeiter.ID" i will need to use a Portal to add childs, which are related to "Personen" and related to "Mitarbeiter". so does anyboday has an idea how to do this? or can explain whats wrong with my database "design"?
  2. I have been out of the Filemaker Pro arena for the past 8 years. I’m currently working to bring myself up to speed on FMP 11 Advance and have run into an issue and I can't seem to get my arms around a solution. First let me start by identifying my primary tables, primary, foreign and match key fields, and the current database schema: tblCONTACTS (fields: [pkCONID] primary, [fkHHID] foreign, [kContact_Type] match key and other fields) tblHOUSEHOLD (fields: [pkHHID] primary and a bunch of address fields) tblHOUSEHOLD_JOIN (fields: [fkCONID] and [fkHHID]) I have a join between tblCONTACTS::pkCONID on the one side and tblHOUSEHOLD::fkCONID on the many; likewise, I have a join between tblHOUSEHOLD::pkHHID on the one side to tblHOUSEHOLD_JOIN on the many. The reason I used the join table is because the Contacts who are labled as "Child" from the [kContact_Type] field can belong in several different households (mom and step-dad, dad and step-mother, etc). In order to get a one-to-many relationship for this specific cohort I added a join table between tblHOUSEHOLD and tblCONTACTS. The CONTACTS table is just as you would expect, a table that contains information relevant to all of the people in the database. The HOUSEHOLD table contains all of the addresses of the people in the CONTACTS table. The field [kContact_Type] in the CONTACTS table is used to distinguish between Children (<18 with no children of their own), and Participants (anyone else). [kContact_Type] field contents are drawn from a value list containing two words, "Child" or "Participant". My ultimate goal: To have the ability to report on Contact activity as a group within the same household [HHID], individually by [kContact_Type]= "Child" or "Participant", and the really tricky part for me… I need to be able to look at these two groups by their roles as they relate to one another: One mom can have many Children, one [Child] will have at least one, morely likely two or more[Participants] a/k/a parents. And not all Participants are parents (some won't have any children). I assume I need a seperate table for these relationship roles but I can't seem to work out how that would work. I tried creating a table occurance based on CONTACTS in a self-join relationship hoping I could link by both the CONID and the [kContact_Type] of "Child" or "Participant"... but naturally that didn't work and I was looking at a mirror image of the main table. I tried seperating the contents of "Child" and "Participant" into two different fields and then creating a self-join... but I still got the mirror image since the join didn't distingish between fields that had null values. Any help you can give me on how I might set this up to work would be greatly appreciated.
  3. I am working on a scheduling module for our production shop. I want to display the Work Orders in a list and Schedule time to each of the Stations between the Work Order IssueDate and ShipDate. Secondly, I would like to report back the actual hours spent vs. the Scheduled time for progress reporting. Tables: Work Order (500/year) WorkOrder# Description IssueDate ShipDate Stations (7-10) StationID StationName Schedule (1 for each Work Order) WorkOrder# StationID TimeEstimated TimeTracking (1000s/year) EmployeeID EmployeeName WorkOrder# DateWorked TimeWorked Employees (20+) EmployeeID EmployeeName Thank you for your guidance. Mark
  4. I have two tables ("Schools" and "People") and I want to be able to have multiple email addresses associated with them. I would like to have one table "Email Addresses" and have a join table that can be used to find which email to pull based on the table and ID of the school/person. What is the best way to do this? I believe it is possible to do this using global fields: Schools "Schools" (global field) ID Name People "People" (global field) ID First Name Last Name Email Addresses ID Type Email JOIN Object to Email table ("People", "Schools") Object ID Email ID But I'm curious if there is a better way to do this.
  5. Hello community, I have two entities, that have a many-to-many relationship. I have my Computers entity, and a Users entity. One user can have many computers, and one computer can be used by many users. I created my Computers and Users tables, plus a join table to have the relationship. The tables are OK, and work fine, I manually tested with setting IDs. My problem is that, on the layouts, I don't know how to technically and concretely relate two records from each table. I tried with external portal, but when I tried, it also creates records that I don't want. Simple: I would like to be on the Computers layout for example, and set a field so this computer is linked to one given user. And the opposite. With what tools can I do that. What related field to put on which layout so I can relate a Computer with a User. Thanks a lot for your help !!
  6. I’ve got a FMPro12 database and there are 3 tables inside: [HitRecords], [Artists], [RE_AR]. Yep, it covers UK chart singles & albums. One disclaimer. I’ve switched from MSAccess so my understanding of some concepts may not be correct. The basic concept is this. ———————————————————— Table [HitRecords]: <ID_RE> index field, autonumber <Title> text field, title of an album/single Table [Artists]: <ID_AR> index field, autonumber <Name> text field, artist name Table [REAR] creates many-to-many relation between [HitRecords] & [Artists]: <ID_RE> number field, related record from [HitRecords] <ID_AR> number field, related record from [Artists] <Main> 0/1 field* * for every record in [HitRecords] there is only ONE record in [Artists] for which [REAR]<Main>=1 EXAMPLE ———————————————————————- Table [HitRecords]: <ID_RE> <Title> 12 Drunk In Love Table [Artists]: <ID_AR> <Name> 345 Jay-Z 456 Beyonce 567 Beyonce featuring Jay-Z Table [REAR]: <ID_RE> <ID_AR> <Main> 12 345 0 12 456 0 12 567 1 Idea is being that when presented in the charts, this hit single would be credited to “Beyonce featuring Jay-Z” but when searching for, say, all Jay-Z hit singles, we would get “Drunk In Love” as well. I created a layout based on [HitRecords] table. Then inserted a PORTAL based on [Artists] table. Linking table is [REAR] of course. Two portal fields are: Artists::Name, REAR::Main All is fine up to that point. I can sort artists within portal and make that record with <Main>=1 is listed at the top. Perfect. PROBLEM ——————————————————————— I created new layout (all HitRecords with corresponding Artists) in Table View: HitRecords::ID_RE HitRecords::Title Artists::Name REAR::Main No matter what I do I always get FIRST Artists::Name as entered in [Artists] table. Can’t make my DB to get Artist:Name for whom REAR::Main=1. In the example above it will always be “Jay-Z” instead of “Beyonce featuring Jay-Z”. So I get HitRecords::ID_RE HitRecords::Title Artists::Name REAR::Main 12 Drunk In Love Jay-Z 0 instead of HitRecords::ID_RE HitRecords::Title Artists::Name REAR::Main 12 Drunk In Love Beyonce featuring Jay-Z 1 In MSAccess I always created separate query first filtering [Artists] table only for records where REAR:Main=1. And that “ArtistsFiltered” query was then linked to HitRecords table. No idea how to do something similar in FMPro. Thanks fore help! Andrzej, Poland
  • Create New...

Important Information

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