Jump to content

LaRetta

Members
  • Content Count

    10,997
  • Joined

  • Last visited

  • Days Won

    151

LaRetta last won the day on October 20 2019

LaRetta had the most liked content!

Community Reputation

508 Excellent

8 Followers

About LaRetta

  • Rank
    Lifelong FM Student

Profile Information

  • Title
    Developer
  • Industry
    Software
  • Gender
    Not Telling
  • Location
    Everywhere

FileMaker Experience

  • FM Application
    18

Platform Environment

  • OS Platform
    Mac
  • OS Version
    High Sierra

Recent Profile Visitors

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

  1. I was suggesting you NOT wrap $layout in quotes. That would be a common mistake. Did you view Comment's file? I suggest you take a look. You can drop all that extra stuff. hahah! We all posted simultaneously! Don't say we aren't quick at assisting folks here on FMForums! 🙂
  2. Hi Steve, How about you create a simple file showing exactly how 1) you are setting that $layout script variable and 2) your Go To Layout[ by calculation] example? Are you wrapping quotes around $layout? 🙂
  3. Hi Steve, you've been receiving advice from two of the top Developers and their suggestions are sound. Using a portal with related records is a VERY SIMPLE technique and process once you grasp the concept. I highly suggest you just take a few moments to understand how a relationship works by reviewing Comment's file. It would take far less time and effort than using AppleScript and it is a basic understanding of FileMaker. I wish you well on your project. 🙂
  4. Here is my documentation on word break rules, taken mostly from discussions here on FMForum over the years and MOSTLY from Comment 🙂 The ampersand and hyphen are word delimiters - but they are not the only ones. There are many more, first and foremost a space, of course. I don't know if there's a comprehensive list, but at least !@%^()≠+[]{}<>≤≥`~|\? are all word delimiters. Word delimiters are not words, so you cannot get them with the MiddleWords() function. space * # ; " = $ € & / ≈ ∏ ‡ Detailed feedback: If I go to FileMaker Pro 11 Help for MiddleWords, the example uses spaces and the note refers to ampersand(&) and hyphen(-) to identify the beginning of a new word. No other symbols are given. I was curious about what other symbols might be able to be used. I created an Excel spreadsheet with the ASCII 255 characters and created text with separators using each of the characters. When I imported it into FileMaker Pro, I used MiddleWords in my calculation, I found that a period (char 46) did not work, I did find the following symbols did work: Char 9 is ", "Char 10 is ", Char 11 is , Char 12 is , " Char 13 is ", Char 32 is , Char 33 is !, Char 34 is ", Char 35 is #, Char 36 is $, Char 37 is %, Char 38 is &, Char 40 is (, Char 41 is ), Char 42 is *, Char 43 is +, Char 44 is ,, Char 45 is -, Char 47 is /, Char 58 is :, Char 59 is ;, Char 60 is <, Char 61 is =, Char 62 is >, Char 63 is ?, Char 64 is @, Char 91 is [, Char 92 is \, Char 93 is ], Char 94 is ^, Char 95 is _, Char 96 is `, Char 123 is {, Char 124 is |, Char 125 is }, Char 126 is ~, Char 128 is €, Char 130 is ‚, Char 132 is „, Char 133 is …, Char 134 is †, Char 135 is ‡, Char 136 is ˆ, Char 137 is ‰, Char 139 is ‹, Char 147 is “, Char 148 is ”, Char 149 is •, Char 150 is –, Char 151 is —, Char 152 is ˜, Char 153 is ™, Char 155 is ›, Char 161 is ¡, Char 162 is ¢, Char 163 is £, Char 164 is ¤, Char 165 is ¥, Char 166 is ¦, Char 167 is §, Char 168 is ¨, Char 169 is ©, Char 171 is «, Char 172 is ¬, Char 173 is ­, Char 174 is ®, Char 175 is ¯, Char 176 is °, Char 177 is ±, Char 180 is ´, Char 182 is ¶, Char 183 is ·, Char 184 is ¸, Char 187 is », Char 191 is ¿, Char 215 is ×, Char 247 is ÷, NOTE: The character ` acts as a word separator on the Macintosh but not in Windows. RULE 1 (period .) one.two = 1 word one.2 = 2 words 1.two = 2 words 1.2 = 1 word RULE 2 (slash / hyphen - colon : comma ,) one-two = 2 words 1-two = 2 words one-2 = 2 words 1-2 = 1 word RULE 3 (single quote ') one'two = 1 word one'2 = 2 words 1'two = 2 words 1'2 = 2 words I think it is very important information. The old links are no longer available from what I can tell, which is why I'm just posting my 'combined-gathered' rules here again.
  5. This seems to be an ongoing problem ... is it the same portal by chance? https://fmforums.com/topic/98701-crashing-with-filter-formula/ Windows has, over its years, suffered from crashing portals. I don't remember the specifics but one issue had to do with corrupt fonts. Have you tried creating a new portal completely? How about on a new layout? Have you ever ran Recover on a copy of that file and see if it still breaks? added: I won't bother testing since I'm using precisely same FM/OS as Michael. I agree completely though, that filtering a portal is not a good idea with many records.
  6. Hi Peter, Credits should be applied, not only after the fact but in the subsequent month - the month the adjustment is made and should never be back-dated. So once a month is CLOSED OUT, it should NEVER be allowed to be changed and records should be frozen to stop all modification to those financial records (such as using a closed date and restricting modification from Security). For the current month, you can even write static but you'd have to tightly control all edits in a transaction fashion. Here is one of many links about transactional handling of invoices: https://www.geistinteractive.com/page/2/?cat=-1 So every month-end, static totals can be written to a table and so can weekly totals (like on a Sunday). Then the current week's entries can be totalled quickly; the combination providing your results. As Wim says, as record counts increase in your LineItems tables, all reporting of invoices will continue to decline in speed if you don't switch to a method of transactional 'static' recording of values and if you ever attempt to run it on mobile without this in place, it'll become unusable. I would never use eSQL() in a calculation field. As for your current needs in resolving your SQL, you couldn't be in better hands.
  7. The problem with using layout-level restrictions on values which must be correct, is that forgetting and placing the field once on a layout with entry to field left ON, and inconsistent data will result. A stored calculation provides safety from this accidental field placement and as Michael says, can be copied because the field can be entered. It'll also allow scrolling.
  8. Hi 1FilemakerMan, If the same User exists as different records in this new table then you did not follow Comment's suggestion of: "You can create such table by importing the user IDs into another table where the UserID field is validated as Unique, Validate always." Can you attach your file? Added: You did NOT import the User ID field and set it to unique, validate always.
  9. I'm struggling to see it as well, Wim. Is there any way you could create an example of it breaking - when using AE serial, for example?
  10. Hi Wim! Can you explain this a bit more? How might users collide if creating multiple records? Do you mean because the file was numbering the records or did you have an additional concern?
  11. A great developer once told me, "Know thy Mod() function, when thou cometh to date calculations." 😀 Hi Barbara! No, I haven't perfected it yet either. Michael and possibly Ray Cologon are the only two who've mastered it to that degree. Nice to see you again!
  12. Hi Rudy, Another option is to use a tool such as Base Elements. A tool such as this is invaluable.
  13. Hi Greg! Comment is correct - no surprise there - that the records should all be in a single table. And since, if a task is not complete, you want it to 'move forward' ... why not have a COMPLETED button and anything not completed and less than or equal to today would be found daily when you sign in. You can then reassign their dates as you wish according to Comment's suggestions. 🙂 I should also mention that the COMPLETED can simply be a dateCompleted if you need to track when you complete a task. It doesn't need to be a boolean 1. The point is, a person will need to decide when a task is complete. Anything NOT complete should automatically be considered to have 'moved forward' without changing its due date at all.
  14. Are you SURE you don't have two layouts named Inventory" BTW, how many layouts do you have (in layout mode, how many total 'records' are listed?
×
×
  • Create New...

Important Information

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