Fitch

Moderators
  • Content count

    4,421
  • Joined

  • Last visited

  • Days Won

    40

Fitch last won the day on March 9

Fitch had the most liked content!

Community Reputation

136 Excellent

About Fitch

  • Rank
    Imaginary friend

Profile Information

  • Gender
    Male
  • Location
    Portland, Oregon

Contact Methods

  • Website URL
    http://www.fitchandfitch.com

FIleMaker Profile

  • FM Application
    15 Advanced
  • Platform
    Cross Platform
  • Skill Level
    Expert
  • Certification
    7
    8
    9
    10
    12
    13
  • Membership
    TechNet
  • Title
    Developer
  • Industry
    Public health
  1. Petrowsky hangs out on the FileMaker facebook group. Bante frequents community.filemaker.com . It seems like this is explained pretty well here: http://filemakerstandards.org/display/bp/Suppressible+Triggered+Scripts Basically, you set a global variable when you want to suppress triggers. And in your triggered scripts, you put at the top something like: If[$$triggersOFF] Exit Script End If That's really all there is to it.
  2. It does sound like you're over-complicating it, but maybe you want to pass Get (LayoutName) as a script parameter?
  3. You could print it to a PDF, would that work for you?
  4. Looks like they use several global variables: $$~TRIGGERS_SCRIPTS, $$~TRIGGERS_DISABLE, and $$~DISABLETRIGGERS You should be seeing those in your data viewer. I don't work with those functions, but I use a similar method.
  5. Can you clarify what this portal is displaying vs. what you want to display? Feel free to attach a screenshot.
  6. I suggest you create number fields in the client table for current balance, Over 30 Days Due, Over 60, etc., and update them with a script as payments and invoices are processed. Stored balances make it easy to the kind of thing you want, and it will keep your system from getting slower and slower as you add more records.
  7. It's important that the backups exclude the live database folder. This is non-negotiable. Also anti-virus should exclude the live databases. Turn off screen saver, turn off indexing. Make sure they open up the necessary ports in your firewall. All this and more is documented: https://fmhelp.filemaker.com/docs/15/en/fms15_getting_started.pdf Make sure the server meets the specs: http://www.filemaker.com/products/filemaker-server/server-15-specifications.html A fast hard drive is extremely important, but fast network is too, so it's possible you may get equal or better performance from your new server. Windows server is actually a very good host for FileMaker. Try to foster a good relationship/partnership with your IT guys. They may have preconceptions about FileMaker based on antiquated information. Good luck!
  8. Have you tried looping through the portal rows? A script can do that very quickly.
  9. Another way to loop through the records without a new window would be to gather all the IDs of the found set into a variable, $ID List for example, then find them one by one using GetValue( $ID List ; $n).
  10. I seem to recall an issue with a memory leak involving new windows. Perhaps you could re-architect the script to avoid popping up 100 new windows. You're only exporting a single field, is that correct? Maybe Export Field Contents would work -- that exports a field in the current record, so you wouldn't need a new window to isolate each record before exporting.
  11. One way to do it is with conditional formatting. Based on the results of a calculation, you can change the color of the text to match the layout background; or, you can change the size of the text to a very large number so that it's pushed outside the boundaries of the field or text box.
  12. Substitute ( fieldname; [ Char( 1 ) ; "" ] ; [ Char( 2 ) ; "" ] ; [ Char( 3 ) ; "" ] ; etc. ... )
  13. Sounds like you'd want to start with a table for items, and a related table for expenses. The Category field could go in either table, or both -- presumably with different values, e.g. banjo category might be "twangy things" and its expenses might have categories like, "parts," "lessons," "accessories," etc.
  14. This is a question that comes up regularly. Not sure there's ever an ideal answer, but here's a few options: 1. Create a table of incident numbers and a script that "takes a number" when creating a new report. 2. ExecuteSQL( select max(number) from table where year = ? ; ""; ""; Year( Get (CurrentDate) ) ) + 1 3. Set Date( 1; 1; Year( Get (CurrentDate) ) ) into a global field with your startup script; make a relationship to your reports date field, and use Max( related::number) + 1 HTH
  15. What is your question?