• Content count

  • Joined

  • Last visited

  • Days Won


comment last won the day on May 22

comment had the most liked content!

Community Reputation

1,345 Excellent

About comment

  • Rank

Profile Information

  • Gender
    Not Telling
  1. Does the attached work for you? Example2.fmp12
  2. I am afraid not. I could not follow this at all. I don't understand what your tables represents in real life (names like FTIME and STEPS are meaningless to me, and the fact that your screenshots use different names only adds to the confusion), and how they are related (or why they are related the way they are). And I don't understand in which table are the times you want to sum. I am not even sure from which table you want to sum them. It sounds like you want to have a subtotal in each portal row? In such case, you must have the start and end dates within the table shown in the portal (STEP???), either as calculation fields or to begin with, and use them in the relationship to the table where the times are. But that's just a wild guess.
  3. I find this very confusing. Which one of your tables is the table of People? The Active field is in Table A, but the CalcNumber field is in Table B - so what exactly does "matching the CalcNumber" mean?
  4. I don't really see what role the checkboxes are supposed to play here. But to answer what I think may be your original question: Suppose you have a value list named "MyValueList" containing 1000 values. And suppose you have a field named MyCheckBoxfield, formatted as checkboxes using the MyValueList value list. In this situation, the following script step: Set Field [ MyTable::MyCheckBoxfield ; MiddleValues ( ValueListItems ( "" ; "MyValueList" ) ; 600 ; 50 ) ] would check 50 contiguous boxes in the MyCheckBoxfield, starting from box #600.
  5. Sorry, I don't know what you're showing me. I mentioned two possible scenarios, and you haven't said which one (if any) is correct.
  6. Are your records numbered with serial numbers? If yes, then in order to find 50 records starting from record #600, you need to input somehow two values: 600 and 50 (say into two global fields). Then your script (surely you would want to script this), can find records with serial numbers in the range between 600 and 649 (the latter calculated from the two supplied numbers). No checkboxes are required for this. If they are not numbered, then I guess (!) you would want to start by showing all records, then omit the first 599 records, then go to record number 51 and omit the remaining records. No checkboxes are required for this either.
  7. You need to link RecordedDimensions directly to either Dimensions or Gages. If the Instrument field in RecordedDimensions is populated to be the same as the Instrument field in the corresponding Dimension, you could define the relationship as: RecordedDimensions::Instrument = Gages 2::Gage Type where Gages 2 is a new occurrence of the Gages table. Then your value list would be defined to use values from Gages 2::Gage ID, include only related values starting from RecordedDimensions. -- Note: this is a technical answer. I don't really understand what you're doing here, or why. And I have a feeling there is a better way to do it.
  8. It's a simple question. The answer should be one word: the name of the table in which the field is defined.
  9. Let's start with this: in which table is the field you need to populate using this value list. Also, am I correct in assuming that your last picture shows records from the Gages table, with the left column being Gages::Gage Type, and the right column being Gages::Gage ID?
  10. I got lost in your description. It seems you're looking for a conditional value list.
  11. In addition, there is really no good reason to nest Case() within If(); you can do it all in a single call of the Case() function: Case ( IsEmpty ( Sub9First_Semester ) or IsEmpty ( Sub9Second_Semester ) ; Sub9Grade_Point_Average / 2 ; Sub9Final_Grade ≥ "96.5" ; "4" ; Sub9Final_Grade ≥ "92.5" ; "4" ; Sub9Final_Grade ≥ "89.5"; "3.7" ; Sub9Final_Grade ≥ 86.5; "3.3"; Sub9Final_Grade ≥ 82.5 ; "3" ; Sub9Final_Grade ≥ 79.5 ; "2.7" ; Sub9Final_Grade ≥ 76.5 ; "2.3" ; Sub9Final_Grade ≥ 72.5 ; "2" ; Sub9Final_Grade ≥ 69.5 ; "1.7" ; Sub9Final_Grade ≥ 66.5 ; "1.3" ; Sub9Final_Grade ≥ 64.9 ; "1" ; Sub9Final_Grade < 64 ; "0" ) Note also that specifying an empty default result is redundant.
  12. What type are your movie files? And are they embedded in the container field, or are they stored externally?
  13. I am not sure what you mean by "API improvements". The runtime limitations are listed here: