Jump to content


Popular Content

Showing content with the highest reputation since 11/10/2018 in all areas

  1. 2 points
    You have to parse this like you would a math expression - from the parentheses outward. First you find the position of the comma: Position ( FullName ; ", " ; 1 ; 1 ) Then you subtract that from the overall length of the full name to get the count of characters on the right side of the comma. And you have to subtract 1 to account for the space after the comma.
  2. 2 points
    A shot in the dark: have you tried Base64Decode()?
  3. 1 point
    First, you could have used a single script and define each button to pass a different parameter value to the script. But even so, creating a button for each product is tedious and redundant. You already have a record for each product in the Products table - why don't you take advantage of that? Show the products in a portal or in list view, and have a button take you to a more detailed view. If you are using a master-detail layout, with a portal to the same table*, you don't even need the button: simply clicking into a portal row will bring you into detailed view of the clicked record. -- (*) Requires version 17. Please update your profile to show your version and OS.
  4. 1 point
    Just an alternative that I've used in similar situations, which I find more readable and understandable: First Name: GetValue ( Substitute ( SUPPLIED NAME ; ", " ; "¶" ) ; 2 ) Last Name: GetValue ( Substitute ( SUPPLIED NAME ; ", " ; "¶" ) ; 1 ) Converting text delimited with a specific string to a list often makes parsing it much easier.
  5. 1 point
    That is indeed good news. I would suggest you extract the parts into two separate fields. Then you will be able to easily recombine them in any way you wish. Use = Left ( FullName ; Position ( FullName ; ", " ; 1 ; 1 ) - 1 ) to extract the last name, and = Right ( FullName ; Length ( FullName ) - Position ( FullName ; ", " ; 1 ; 1 ) - 1 ) to extract the first.
  6. 1 point
    I am afraid you will need 2nd grade math for this - but I will try... Consider this: Case ( BillableWeight ≤ .5 ; "A" ; BillableWeight ≤ 1 ; "B" ; BillableWeight ≤ 5 ; "C" ; BillableWeight ≤ 10 ; "D" ; "E" ) What this means is that: when BillableWeight is between 0 and 0.5, the result will be "A"; when BillableWeight is between 0.5 and 1, the result will be "B"; when BillableWeight is between 1 and 5, the result will be "C"; when BillableWeight is between 5 and 10, the result will be "D"; when BillableWeight is above 10, the result will be "E". Why? Because when BillableWeight is say 4, the first test returns false: 4 is not ≤ .5. The next test, BillableWeight ≤ 1, also returns false. The third test returns true, and the result will be "C" as expected, since 4 is between 1 and 5. So our Case() statement does evaluate if the given input falls BETWEEN 2 boundaries; but we only need to list each boundary once (provided we do so in the correct order).
  7. 1 point
    That option is hidden unless you hover the mouse over the post. Perhaps that should be always visible?
  8. 1 point
    I can tell you how I usually do this. I start with something like the following code in the web viewer: "data:text/html," & Substitute ( Table::HTML ; [ "$placeholderA" ; Table::SomeField ] ; [ "$placeholderB" ; Table::AnotherField ] ; [ "$placeholderC" ; Table::ThirdField ] ) Then I work on the HTML code in the HTML field, until I get it functioning the way I want. Once that is done, I open the Data Viewer and type = Quote ( Table::HTML ) I copy the result and paste it to replace the Table::HTML part in the web viewer code.
  9. 1 point
    If you love FileMaker but are new to JSON, download this free educational tool and start learning! http://www.filemakerforever.com/articles/134
  10. 1 point
    Try this: create a summary field, set it to count the primary key, and be a running count. Put this on the layout.
This leaderboard is set to Los Angeles/GMT-08:00

Important Information

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