NewBoard

Members
  • Content count

    18
  • Joined

  • Last visited

Community Reputation

0 Neutral

About NewBoard

  • Rank
    member

FIleMaker Profile

  • Profile Updated
    05/19/2017
  • FM Application
    16 Advance
  • Platform
    Windows 10
  • Skill Level
    Beginner
  • Title
    Quality Assistant
  • Industry
    Automotive
  1. Thank you comment this did the trick!
  2. I currently have a form that contains a portal. In the portal there is a value that will either be "Accepted" or "Rejected". I'm wondering if there's a way to parse through this table to check if any related values have a "Rejected" or if they are all "Accepted". Then using that outcome, decide if the form should display Rejected or Accepted. Please let me know if I need to provide any more information and/or images. Thanks in advance for any assistance you can offer!
  3. Oh my gosh. Thank you so much Fitch. You have solved something that I've been stuck on for a few days now. This worked perfectly!
  4. That won't work for me unfortunately. I don't have a simple relationship like that. I have Lots, tied to Part Revs, tied to Parts
  5. I have a table that contains dimensional data for parts. Each record has a unique ID, but also has another field with the ID associated with the part. I have another table that I'll be storing individual inspection data on. I was wondering if it's at all possible to parse the first table, and copy over all records that have a specific part ID to the second table whenever someone starts a new inspection record. Please let me know if I need to provide any more information and/or pictures. Thank you in advance for any assistance you can offer!
  6. I answered your question. RecordedDimensions
  7. Your assumption is correct. So, I currently have one form for building the parts. This is where the manager will enter in what dimensions are being inspected, what tools, and the tolerances through a portal linked to the Dimensions table Then, as the inspections are actually performed, they will pull up the following screen: The portal on the left contains all of the information that the manager entered in earlier. I want the user to be able to enter information into the portal on the right, which points to the table RecordedDimensions. Which I have working correctly besides the instrument dropdown.
  8. A conditional value list is exactly what I'm trying to make. It's a little easier said than done though, since I'm storing values in one table, but referencing them in another. Currently when entering values, my stored values table doesn't know which report from the Dimensions table it's referencing. If I could figure out how to the dimensions and stores values 1-to-1, I could do a conditional value list. I've managed to get the drop down to only show Gage ID's related to the gages used in the inspection. However, it shows ID's from all of the gages used on that inspection. Whereas I want it to only show the ID's for the gage used on that specific dimension. Let me know what I can clarify for you.
  9. I am currently building a database to handle the inspection sheets used by our Quality lab. Here is the relationship layout: For each revision on the Revisions table, I have a differing number of Dimensions that need to be measured (some parts/revs will have 5 dimensions, while others will have 15). Each dimension has a specified type of instrument used in measurement, and a max/min value. The instrument used is a drop down menu that references a list of instruments/gages that we use. Here is how I have my inspection sheet currently laid out: The portal on the left points towards my dimensions table. It shows the data corresponded to the specified Part Number and Revision level. The data contained in this portal is uneditable from this form. The portal on the right points towards my RecordedDimensions table. It will store data that will correspond back to the Lot# associated with that inspection sheet. I also have a table that pairs all the different types of instruments we use, with their corresponding gage ID's: Now I would like my user to be able to click on the dropdown box under Instrument#, and that drop down box will only show the Gage ID's for the specified gage. So, if on the dimensions table, a dimension calls out for Digital Micrometers to be used, then when my user goes to select the instrument ID (which is saved in the RecordedDimensions table) it will would allow them to choose 151, 152, 153, 306, 324, 330, and 331. Please let me know if I have not provided enough information/pictures, I will gladly provide more. Thank you in advance for any assistance you can offer me!
  10. I ended up keeping the customer's their own separate table. However, I linked them directly to the parts list. That has seemed to work as intended. What was the advantage to having the third table joining the two?
  11. I am designing a database for the inspection sheets used in our quality lab. Each of our parts has a different number of criteria that they need to be inspected for. This ranges anywhere from 5-15 dimensional requirements. I am wondering if there is anyway in FileMaker to display a varying number of both editable and uneditable fields. So for instance if somebody pulls an inspection sheet for a part with 6 different dimensional requirements, FileMaker will only show 6 uneditable fields describing the dimensions in question, and 6 editable fields for the user to type in their measurement. Then, if somebody pulls an inspection sheet with 10 dimensional requirements, it will display 10 instead. Thank you for any assistance you all can offer!
  12. I have to ask, why did you split part numbers and customers? Wouldn't it be easier to have a field for customer within the Part Number table?
  13. Okay this looks like exactly what I need. Thank you very much, you are a life saver! I'm just wondering though, how does the CustomerPartsJoin table know which parts go with which customers? Will I have to manually enter the foreign keys for each on that Table? Edit: I'm actually having quite a bit of trouble with this relational setup. Forms connected to the CustomerPartsJoin can find my customers and part numbers exactly as intended. However, I'd like forms related to Revisions (and Inspections eventually) to have a drop-down menu to pick a part number and customer. Trying to do so yields no desirable results, as all drop down menus I attempt to tie to Customer or Part number are completely un-useable. This is the List View of the CustomerPartsJoin table. I have hidden the Customer UUID selector behind the Customer Name box. I can freely chose customers and part numbers here. This is the form view for the Revisions table. I have tried all sorts of combinations for the drop down menus. I've tried pointing them to the CustomerPartJoin table, pointing them to their own original Parts/Customer tables, pointing them at the UUID of the CustomerPartJoin table. All to no avail. I'm thinking that I'm just missing something very obvious as I'm still new to FileMaker. Or maybe it's not possible to do what I'm trying to do with the current relationship setup.
  14. I currently have a three table relationship going. The top layer just has part number and customer number. This table will have new entries on it, but should never really change besides that. The next layer contains the part number, part description, part revs, and a UUID. This is linked to the first table via the part number. The final layer is where all of the inspection data will be stored. This is linked to the first layer via UUID. This is really where I need FM to be able to retrieve data from only the top rev.
  15. How would I go about doing this?