• Content count

  • Joined

  • Last visited

  • Days Won


comment last won the day on January 14

comment had the most liked content!

Community Reputation

1,282 Excellent

About comment

  • Rank
  • Birthday

Profile Information

  • Gender
    Not Telling
  1. Your question is rather confusing, esp. the part about "button script trigger". If you have a button defined to run a script, then no script trigger is necessary. Make your script do something like: If [ Details::Type = "Meeting" ] Go to Layout [ "Meeting" ] Else If [ Details::Type = "Interview" ] Go to Layout [ "Interview" ] Else If [ Details::Type = "Incident" ] Go to Layout [ "Incident" ] # add more as necessary End If
  2. A relationship using the X relational operator does not need a matching key value. Just use any two fields as the matchfields. -- P.S. What makes you think Filemaker is not a "true relational database"?
  3. I don't know, because I don't understand the situation. There are numerous options here, depending on what exactly you're tracking and - no less importantly - for what purposes. These questions cannot be sidestepped.
  4. Why don't you relate the StaffList TO directly to Workshops?
  5. Set Field [ Installations::cWeek ; Get(CurrentDate) - DayOfWeek ( Get(CurrentDate) - 1 ) - 6 ]
  6. If you want to group them by week, you will need to add a cWeek calculation field in that table, too. Then the process of finding becomes the same as outlined above. As for the additional sub-grouping, it's only a matter of adding more sub-summary parts and sorting the records accordingly.
  7. Do you only need to find them, or do you also need to group them by week, like you did with the installations?
  8. This part is not clear: If they have different dates. then why wouldn't they be separate records, entered individually as they occur, and share a common category or subcategory? What ties them together as single item?
  9. Yes, the Go to Field[] script step (if used in a script) will override the disabled entry behavior. But denying entry to a field does not make it modifiable "only through a script" - so your strategy may need rethinking.
  10. It's difficult to follow your explanation, because you use inconsistent terms. Price is not the same thing as Cost - and Price/Cost is yet another. Also, so far you have been subtracting the fee, now it seems you want to add it. If I take the following formula: Let ( [ charge = MSRP * ( 1 - Coupon Discount ) ; fee = charge * .0225 ] ; charge + fee - Price ) and plug in the following values: MSRP = 238.16 Coupon Discount = .25 Price = 150.16 the result will be 32.47895.
  11. Try = If ( Deposit ; Amount - Deposit )
  12. You can replace FeeRate with the actual rate (number). But if you ever need to change the rate, it will affect all your records, not just the future ones.
  13. FeeRate is a field that will hold the fee rate - i.e. the percentage of the charge that will constitute the fee amount. Well, what do you think?
  14. If I understand this correctly (and that's a very big if), you want to do: MSRP * ( 1 - Discount ) * ( 1 - FeeRate) - Cost Which could be rewritten to be more readable as: Let ( [ charge = MSRP * ( 1 - Discount ) ; fee = charge * FeeRate ] ; charge - fee - Cost ) If you populate the FeeRate field with the value of 0.0225, the result will be 28.3125 for both. Resist the urge to hard-code the fee rate into the calculation formula.
  15. Well, if: MSRP = 100 Discount = 25% CC Fees = 1.69 Cost = 45 then: MSRP - MSRP * Discount - CC Fees - Cost will return 28.31. Although I would prefer to write it as: MSRP * ( 1 - Discount ) - CC Fees - Cost -- Suggested reading: PEMDAS