Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


comment last won the day on September 12

comment had the most liked content!

Community Reputation

1,408 Excellent

About comment

  • Rank

Profile Information

  • Gender
    Not Telling

Platform Environment

  • OS Platform
  • OS Version

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. If you mean how to produce quoted text as a result of a calculation formula, try = "\"9/26/2018 3:00 AM\"" or = Quote ( "9/26/2018 3:00 AM" )
  2. This doesn't answer my question regarding the type of the field (or the type of calculation's result, if it is a calculation field). Assuming it is text, the rules applied during find will be the rules for finding text and characters and Filemaker will not recognize the timestamp values as such. Looking at your example, you are searching for three words: "9/26/2018", "3:00" and "AM" - and all three are present in the found record. If you want to find the exact value "9/26/2018 3:00 AM" you must enclose it in quotes. Alternatively, you could store the values individually as timestamps in a related table and search there. But it seems like the best solution would be to search the start and end fields directly. I really cannot see why you need the list.
  3. Is the timestamplist field a Text field, containing a return-separated list of timestamp values?
  4. Uncheck the 'Allow user to override ... ' option in the Validation tab.
  5. comment

    Rebuilding an Index

    The TextStyleAdd() function does not modify the actual characters stored in the field - it merely styles them for display. To achieve your stated purpose, you need to use the Proper() function (and you should also add TextFormatRemove() to undo what you did).
  6. See: https://fmforums.com/topic/67941-having-two-fields-with-no-duplicated-data/?tab=comments#comment-322406
  7. comment

    Simple XML Export but to include repetitions

    Try it this way: <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fmp="http://www.filemaker.com/fmpxmlresult" exclude-result-prefixes="fmp"> <xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/> <xsl:template match="/"> <JOB> <xsl:for-each select="fmp:FMPXMLRESULT/fmp:RESULTSET/fmp:ROW"> <PrimaryKey><xsl:value-of select="fmp:COL[1]/fmp:DATA"/></PrimaryKey> <WTN><xsl:value-of select="fmp:COL[2]/fmp:DATA"/></WTN> <Customer><xsl:value-of select="fmp:COL[3]/fmp:DATA"/></Customer> <xsl:for-each select="fmp:COL[4]/fmp:DATA"> <xsl:element name="Colours{position()}"> <xsl:value-of select="."/> </xsl:element> </xsl:for-each> </xsl:for-each> </JOB> </xsl:template> </xsl:stylesheet> Note: Numbered elements are considered bad XML practice (just think how difficult it would be to process each color in a subsequent transformation).
  8. Start by substituting the existing separator with a carriage return to get a return-separated list. Then use GetValue ( $list ; $i ) to get the individual keyword values, increasing $i until it reaches ValueCount ( $list ). Note: Not sure what you mean by "better manipulated in various ways". Filemaker is pretty good at manipulating return-separated lists, so it could well be all that you need to do.
  9. comment

    Timestamp Conversion

    Well, if you had said: SerialIncrement ( "00" ; Month ( TimestampField ) ) & SerialIncrement ( "00" ; Day ( TimestampField ) ) & Year ( TimestampField ) & SerialIncrement ( "00" ; Hour ( TimestampField ) ) & SerialIncrement ( "00" ; Minute ( TimestampField ) ) I wouldn't argue mine was better. But SerialIncrement() exists since version 7, using Right() for padding is really old.
  10. comment

    Timestamp Conversion

    To get the leading zero when the month is a single digit (as it is now). Your calculation will return the same result only for the months of October, November and December. We'll see about that...
  11. comment

    Timestamp Conversion

    Not sure what you mean by that.
  12. comment

    Timestamp Conversion

    Assuming you meant "MMDDYYYYHHMM" (i.e. 4 digit year), you could do simply: SerialIncrement ( "000000000000" ; 10000000000 * Month ( TimestampField ) + 100000000 * Day ( TimestampField ) + 10000 * Year ( TimestampField ) + 100 * Hour ( TimestampField ) + Minute ( TimestampField ) )
  13. comment

    Tuesdays in a year

    A year has either 365 or 366 days. In the first 364 days, there will always be 52 Tuesdays. That's because 364 days are 52 periods of 7 days each, and each of those periods will contain one Tuesday, regardless of which day the year started. Now, a year will have 53 Tuesdays if either day #365 or #366 is a Tuesday. You can test for this by checking if the year starts on a Tuesday (if it does, then day #365 is also a Tuesday), or if the year ends on a Tuesday (if it does, then either day #365 is a Tuesday, or the year is a leap year and day #366 is a Tuesday): Let ( [ first = Date ( 1 ; 1 ; Year ) ; last = Date ( 12 ; 31 ; Year ) ] ; 52 + ( DayOfWeek ( first ) = 3 or DayOfWeek ( last ) = 3 ) ) Actually, that would return either 53 or 54. In any case, it wouldn't tell you anything about the number of Tuesdays in that year.
  14. comment

    How to show record number in sub-summary

    Use a summary field defined as Count of [any field that cannot be empty], Running count, Restart summary for each sorted group. That would create a conflict when two users want to produce different reports.
  15. How about = MEDIASIZE * If ( PatternCount ( MEDIASIZE ; "GB" ) ; 1024 ; 1 )

Important Information

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