Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Fitch last won the day on March 19

Fitch had the most liked content!

Community Reputation

169 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

Platform Environment

  • OS Platform
  • OS Version
    High Sierra and Win 10

FileMaker Partner

  • Certification
  • Membership
    FileMaker TechNet

Recent Profile Visitors

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

  1. That's a good example. The number of questions and the reporting requirements of course would factor in to which approach to take. How would you display the min/max/averages in your scenario?
  2. All I suggested was that you could have multiple fields in a table. Attributes of an entity. Like I said earlier, I've built questionnaire/survey systems. Sometimes it makes sense to store the answers as individual records. But then to analyze the data I would say does require a fair amount of effort, e.g. to build a pivot table. Other times it makes sense to store the answers as fields. E.g., we use a Case Log database in my office (public health) to gather data for certain types of outbreaks. Each symptom (cough, headache, fever) is a checkbox on a case record. From this we can produce epidemic curves and other analyses, with relatively little effort.
  3. Including multiple data points in a record does not preclude meaningful analysis. Just sayin'.
  4. Haven't looked at your file yet. But the type of structure you described above is typical of a system that is used for building surveys. I.e., it's made to be flexible so that questions can be added on the fly without adding new fields. I have built such systems. But is that really what's needed here? I'd consider a drastically simpler model where you simply add questions as fields to the Survey table and get rid of all those other tables.
  5. First thing to check is that the fields are actually in the portal. They may look like they are but the way to tell for sure is to click the portal so it's selected -- don't select the fields, just the portal -- and then nudge it up or down with the arrow key. Did the fields move? If not, that's your problem.
  6. https://community.filemaker.com/en/s/feed/0D50H00006ezLwLSAU
  7. It's a Windows bug and there have been reports about it for years. It's super annoying. Sometimes you can get to the selection you want by using the arrow keys. Only other option is to restart the app.
  8. Double-check the 8.1 updates? Windows 8.1 Standard Edition Windows 8.1 Pro Edition System updates 2919355 and 2999226
  9. This can be done with some extra work using script triggers. Something like this: https://www.filemakermagazine.com/videos/endless-picture-sliders
  10. There was an under-the-hood session at a recent DevCon where the engineer from FileMaker stated that object visibility is the first thing evaluated when drawing a layout. If my understanding of this is correct, then Tony's conjecture above is incorrect. I.e., at least in terms of screen redraw you will not incur any performance penalty from hidden objects. However, each hide calculation must evaluate, so that will have a cost -- probably minimal from your example.
  11. You want to change the default style. So save the change to the Default style. Don't save it as a new style, and don't save it as a new theme. Make sure the field is set as Default style. Change the font. Save Changes to Current Style. Then Save Changes to Theme.
  12. Not sure what you're asking. You want to calculate the Opening Stock? Balance + Sold - Purchased
  13. Maybe I didn't explain it well, but if you save a change to the Default style, and you save that change to the theme, that will change the default for fields added to the layout. I tested it and it works.
  14. In Layout mode, hit ctrl-I or go to View > Inspectors > Inspector. Click on either the Styles or Appearance button (the 2nd and 3rd icons at the top of the Inspector). Select your field. Look at the Inspector, it will probably indicate you're using the Default style. Make a change to the field's style or font. Notice the triangle to the right of the field in the Inspector is now red, indicating you've overridden the saved style. Click the triangle and save the style. Notice the triangle to the right of the theme is now red. Click it to save the theme. You have now changed the default for this theme in this file. There's no built-in way to change this for all new files, but you can easily import your saved theme into a new file.
  15. Philip -- I "chickened out" of doing all your work for you? Wow. You're welcome. The reason you got the other email was that after I posted that formula, I realized it would fail if both Random calcs landed on zero, as you discovered. So I deleted the post.
  • Create New...

Important Information

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