Jump to content

Fitch

Moderators
  • Content count

    4,481
  • Joined

  • Last visited

  • Days Won

    47

Everything posted by Fitch

  1. Totalling fields from a related table?

    Sorry I didn't word that right. I meant that a summary field can only summarize data from its own table.
  2. Totalling fields from a related table?

    As you discovered, Summary fields only work on the current context's table. You best bet might be to 'pipeline' the Area data from the Parcel table into a calculated field in the Neighborhood table. I.e., make a calculated field in Neighborhood like so: related::parcel. You can then summarize this field.
  3. Where is my value list being used

    1. Yes, and data you enter after the change will be field 2, whereas existing records would have values from field 1. 2. You should update your user profile so we know what FileMaker version you have. If you have FileMaker Advanced, you can run a Developer Design Report which will list references. However, it's much easier to get this info if you import the DDR into a tool such as Inspector, BaseElements, or FMPerception.
  4. Googling 'FileMaker transactions' returns what you're looking for, I think. For example: http://www.modularfilemaker.org/module/transactions/
  5. Take a look at the attached. In future please zip your file and attach it here -- it's not very appealing to click an untrusted download link. MASTER_POS-Ploblem.zip
  6. Still not clear (although I think you're saying the same thing I said). 1. What did you expect to happen? (What do you mean "group"? You want to add +1 to the Quantity field?) 2. What actually happened? 3. What have you tried? Somewhere on this site there's a description of how to ask a good question.
  7. Looks good. Nice job handling the Commit. One thing you might consider is using GTRR to open the card window rather than Open + Find.
  8. It's not clear what you're asking. If your issue is that duplicate lines for a given product are being added to an invoice, then your script will need to use a Find or use the invoice/line items relationship to handle this.
  9. Highlight Calculation

    Unfortunately Conditional Formatting wasn't invited to the CSS party. See: https://community.filemaker.com/ideas/1124
  10. Insert Calculated Result Bug

    It does sound like a possible 16.0.x issue. Just thought I'd add: it makes sense that this was an old script. In old versions of FileMaker, you had to use Insert script steps for those kind of calculated strings in Find mode -- Set Field wouldn't work. I don't recall exactly when this changed, but for some years we've been able to use Set Field this way, which is generally preferable for the reasons Josh mentioned earlier.
  11. 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.
  12. 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.
  13. 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.
  14. Layout sharing?

    Maybe you should look into the separation model.
  15. 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.
  16. 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).
  17. 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.
  18. 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
  19. 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.
  20. Conditional Formatting vs. Hide Object When

    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.
  21. 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
  22. 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.
  23. Un able to Export Reocrds as fmp12

    Thanks for reporting back -- that's an obscure one for sure! Good job.
  24. 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
  25. 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.
×

Important Information

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