comment

Members
  • Content count

    27,344
  • Joined

  • Last visited

  • Days Won

    497

Everything posted by comment

  1. More details would be useful, especially how this field is being used in relationships. An unstored calculation field cannot be used as the matchfield on the "child" side of a relationship - more precisely, the side from which the relationship retrieves the related record/s. In some cases there are workarounds that can be employed to overcome this limitation.
  2. 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
  3. 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"?
  4. 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.
  5. Why don't you relate the StaffList TO directly to Workshops?
  6. Set Field [ Installations::cWeek ; Get(CurrentDate) - DayOfWeek ( Get(CurrentDate) - 1 ) - 6 ]
  7. 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.
  8. Do you only need to find them, or do you also need to group them by week, like you did with the installations?
  9. 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?
  10. 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.
  11. 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.
  12. Try = If ( Deposit ; Amount - Deposit )
  13. 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.
  14. 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?
  15. 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.
  16. 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
  17. As I said back in April, this is easy to do with a vertical arrangement. Sort the found records by cWeek and by product and show them using a list layout with two corresponding sub-summary parts and no body part. Use a summary part defined as Count of [any non-empty field] to provide the counts.
  18. I am afraid I don't fully understand what you're saying. To get the kind of display your screenshot shows, place the related CompanyName field on the layout, make it non-enterable, and use it to cover the local CompanyID (foreign key) field that has the value list attached to it. When they click on it, the underlying field will activate and they will get a drop-down (or pop-up) to select the name from. The alternative where they would actually select the name is much more complex: you would have to define another relationship to another occurrence of the Companies table, and use it to make the local CompanyID field lookup the corresponding value from there. Note that you can also select from portals or list views. -- P.S. Please update your profile to reflect your version and OS.
  19. Not sure what is the "consistency" that the picture is supposed to demonstrate.
  20. You're not telling us how the URL needs to look, so it's hard to say what's the best way to build it. In general, you can use the List() function to get a list of (non-empty) values in each related field. Also, if you're looping, you can save resources by using a script variable to build the URL.
  21. The simplest way is to define a value list using values from the CompanyID field, also displaying values from the CompanyName field, and set it to 'Show values only from second field'. It will look as if you're selecting the name - but the value entered be will the ID.
  22. Yet another option: sort the found records by the DeliveryRemaining field, ascending (or descending) and check the value of the last (or first) record.
  23. Copy and paste is in the province of the users. You (the developer) shouldn't use it, unless the script is meant to assist the user in data entry. Clicking on the background commits the record, and that's what your script needs to do too - sorry for not making that clear. I don't think you need to do anything beyond that, unless you run into refresh issues.
  24. Is that a Filemaker plugin?
  25. I am not sure I follow your description fully. It looks like you would want to perform Constrain Found Set (in a new window, to preserve your current found set) and see if any records are found. Or, if you are looping, you could something like: Go to Record [First ] Loop If [ YourTable::DeliveryRemaining ] Set Variable [ $rem ; 1 ] Exit Loop If [ 1 ] End If Go to Record [Next; Exit after last ] End Loop If [ not $rem ] # ALL RECORDS HAVE 0 REMAINING End If