Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Fitch last won the day on January 13

Fitch had the most liked content!

Community Reputation

154 Excellent

About Fitch

  • Rank
    Imaginary friend

Profile Information

  • Title
  • Industry
    Public health
  • Gender
  • Location
    Portland, Oregon

Contact Methods

  • Website URL

FileMaker Experience

  • Skill Level
  • FM Application
    16 Advanced

Platform Environment

  • OS Platform
  • OS Version
    El Capitan and Win 7

FileMaker Partner

  • Certification
  • Membership
    FileMaker TechNet
  1. Have you tried restarting the computer? If that doesn't work you might need to re-install FileMaker.
  2. Always Verify backup integrity?

    I think your idea is OK. Set the server to not open the files automatically. That way, if there's a crash, you can restart the machine and open up the files in FileMaker Pro (client) to do a consistency check before hosting them. But even that is optional if you're talking about restoring from a backup vs. the crashed live files, because the consistency check would run on the daily backup so you'd find out then if there was an issue. Just depends how high the stakes are for you. If they're that high you probably should be running progressive backups -- maybe instead of the hourly.

    Going back to your original post, there's a big red flag there that hasn't been discussed: it's almost never a good idea to use ExecuteSQL as a calculated field, or any layout calculation (tooltips, conditional formatting etc.). There's been quite a bit written about this, but essentially the deal is that if there are uncommitted records in the table you're searching, the client will attempt to download the entire table from the server. Not a pleasant experience. Bottom line is, only use ESQL in scripts, where you can control it a little better. When used appropriately it's fine with large data sets. 265k is large-ish but FileMaker can handle millions of records no problem, it just depends on the design. Since you're familiar with SQL this link will have a lot you already know but you may find some FileMaker-specific tidbits: https://filemakerhacks.com/2012/10/19/the-missing-fm-12-executesql-reference/ About the profile, I share your concerns about collecting personal info. We have to register people with an email address to prevent spam. The rest of the profile is completely optional. However, it really does help us -- a lot! -- to answer questions if we know what version of FileMaker, what platform and what level of experience you have. Also FYI this forum is pretty much run by @Ocean West as a labor of love. I hope the ads cover his hosting costs but I don't know. He is a fellow FileMaker developer who's been supporting the community for as long as FileMaker has been around. I know he takes data privacy seriously.
  4. Is your text in a text object? I.e., it's not in a field, it's directly on the layout? You can't perform calculations directly in text objects. In order to use the calculation you want -- Year(Get (CurrentDate))-1 -- you'll need to create a calculated field (or a field where you set the calculation using auto-entry or a script, or use a script to set a global variable). Make sure the storage of the calculated field is set to unstored so it will always update. You can then use Insert > Merge Field (or Merge Variable) to insert the field or variable into your text.
  5. MiddleWords is not restricted to paragraph delimiters. You may be thinking of MiddleValues. So if the data has a consistent separator, you don't need to do any substitution, you can simply parse it out as in Lee's last post. Handy reference: Word Separators
  6. Hacking concerns of startup scripts?

    There's nothing wrong with an opening script trigger. It only becomes an issue when people try to use scripts instead of the security settings. It sounds like you are taking appropriate measures. You may want to suggest number 2 as a product idea.
  7. Layout interfering with OnObjectExit Script?

    Try putting Exit Script[ 0 ] as the last step in your triggered script.
  8. How to best determine login type?

    Get(HostName) might be useful. What is the actual issue you're trying to solve? Also: Get ( ConnectionAttributes ) Get ( ConnectionState ) Get ( FilePath ) Get ( HostApplicationVersion ) Get ( UserCount )
  9. Active window

    A $$variable is specific to a file. If each window is from a different file, then they'd each have their own $$variable.
  10. I know this isn't really an answer to your question, but since nobody has chimed in... personally I wouldn't be pleased to have to select a number from a list when I could easily type in a number. Like when a credit card form makes me select a month or year for expiration. I know it may help them, but from my perspective it insults my intelligence and is annoying. Is it really so bad just typing in the number? If so, maybe there's some other approach? What's the ultimate goal -- why are they doing the sort?
  11. If each record already has a date, that might be sufficient. Even if it does, it can be useful to have a field for the quarter and/or month and/or year. Depends on the kinds of reports you want to produce. As Mike said, it's hard to say without seeing a data sample, but 200k records a year is not unusual for a FileMaker solution. After 10 years you'll have 2 million records, and that should be fine. If things start to slow down you can explore archiving or data warehousing options.
  12. I think using Substitute to ignore them is fine, unless you really want to count them -- then I'd probably put them in their own $wordList "bucket" (or put them in the $count = 1 bucket).
  13. You don't need a new layout or new tables. You should be importing the data to new records. Then you can simply do a Find to call up whatever quarter(s) you want to look at. Welcome to the forums.
  14. Data Mining in a found set

    One thing you can try: when you're on the found set, choose Window > New Window, then when you're in Find mode, rather than Perform Find, choose Requests > Constrain Found Set. Close that window when you're done, and you'll be back at your starting window with your original found set. Repeat as needed. There are other ways that may be more efficient if you're going to script this. The info above would be for doing it without a script.
  15. Prorata calculation

    I'm not sure what your issue is -- you just stated the calculation yourself: ( full monthly amount / 26 ) * prorata days You could define this as a calculated field, or a number field with an auto-enter calculation, or you could use a Set Field script step attached to a button. You'll probably want to use the Round function as well. Does any of that help? Welcome to the forums!

Important Information

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