We have reset all users FileMaker related profile fields. Please take the opportunity to update your information,  this will provide background to members whom read your posts. Click here.

Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Fitch last won the day on June 4

Fitch had the most liked content!

Community Reputation

146 Excellent

About Fitch

  • Rank
    Imaginary friend

Profile Information

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

Contact Methods

  • Website URL
  1. Layout sharing?

    Glad I could help. FYI in FileMaker 16 you can now set the data source as a variable, so it can be scripted.
  2. Schema design for small project...

    I'd lean towards using a table for the Y/N/NA items, but with separate (boolean) fields for Y/N/NA. And the actions in the parent record, again with separate booleans for each. Makes the reporting dead simple.
  3. Email List Calculation

    Glad I could help. And yes I meant a new table. Any time we see something like field1, field2, field3, that's generally a red flag that the database structure might need rethinking.
  4. Layout sharing?

    Maybe you should look into the separation model.
  5. Email List Calculation

    First of all, don't use IsValid when you're actually testing for IsEmpty. I'd suggest further that this is unnecessary here, because List will remove the blanks for you. Now to answer your question, you're on the right track with the List function, but you don't need to do all that calculating of the trailing semicolon. Just wrap the List calc in a Substitute function, replacing ¶ (carriage returns) with semicolons. I'll go a little further and suggest that you put all the email addresses in a separate table. That way you just need one email field and one flag field (and maybe a 'sort' field). You could then grab them all through a (possibly sorted) relationship* like so: Substitute( List( flaggedEmails::email ); ¶ ; "; " ) *Or you could do it via ExecuteSQL.
  6. Restricting data by month

    You're on the right track, but the problem here is that the script would trigger after you've already landed on the layout so the server would still have to download whatever records happened to be in the found set. You should create a simple layout that's based on a layout with zero (or very few) records. Set this layout as your startup layout. Attach this script to a button on that layout: Enter Find Mode Go to Layout[ invoice list] Set Field[ date ; Month ( Get ( CurrentDate ) ) & "/" & Year ( Get ( CurrentDate ) )] Perform Find You don't incur a penalty when you go to Find mode before you go to a layout. The server doesn't download data until you go back to Browse mode (after the Find).
  7. I think Barbara is right about List view vs. Form, but I'll have to check. You're right about containers, they won't download unless they're visible.
  8. To clarify a couple of points: - When you're on a form view with no fields, no data is fetched. - If ONE field is present, then ALL data from THAT RECORD is fetched. I.e. ALL FIELDS from that record. The other big difference in form view is that you're only viewing ONE record. In table or list view you might be looking at many records. Check out server under the hood for more: https://youtu.be/VCrNP4VZiM4
  9. Card has the huge advantage of being essentially a new window -- that means it can display a completely different layout. There's not much downside to cards -- it does require building a layout, and both the parent and card window can't be moved until the card is closed. That's about it.
  10. Can't remember where I heard this, possibly a Devcon session, but as comment noted: with Hide Object, the layout rendering engine does not have to draw the object at all. So it should be theoretically if not perceptibly faster. I also find it helpful when I'm looking at a layout to be able to distinguish which objects are actually getting formatted vs. those that are being hidden.
  11. Copying associated data between tables

    There are various ways you could do it. For example, you could create a script to get a list of the desired dimensions, and then loop over that list to create new records in the target table. So something like: Set Variable[ $source ; ExecuteSQL( "SELECT theID WHERE partID = ?" ; "" ; "" ; inspection::partID ] Set Variable[ $count ; ValueCount( $source ) ] Go to Layout[ the target table for the new records ] Loop Set Variable[ $i ; $i+1 ] Exit Loop If[ $i > $count ] New Record Set Field[ partID ; GetValue( $source ; $i ) ] End Loop
  12. FM 16 bottom toolbar

    Frankly I'm surprised that the toolbar toggle button worked before, when the command wasn't in the menu set, since that's what happens to the icons in the toolbar -- they'll be dimmed out if the command isn't in the menus. Anyhow, glad you have a solution.
  13. Un able to Export Reocrds as fmp12

    Thanks for reporting back -- that's an obscure one for sure! Good job.
  14. The paid membership only gives you a "preview" download, typically close to release date. To be an actual beta tester you'd need to contact the product manager at FileMaker. Anyone can suggest product ideas, though. https://community.filemaker.com/community/discussions/product-ideas
  15. FM 16 bottom toolbar

    In fact the shortcut does work if the menu is off. I think maybe I see what's going on -- you have a custom menu that doesn't include the Status Toolbar command in the View menu. So if you hide menus, there's no way to toggle it back on. That's the only thing I can think of that makes sense. If that's the case, it will be a very simple thing to fix, just make sure Status Toolbar is included in your custom menu.