Jump to content

Rich

Members
  • Content Count

    56
  • Joined

  • Last visited

Community Reputation

1 Neutral

About Rich

  • Rank
    member

Profile Information

  • Title
    Technologist
  • Industry
    Education
  • Gender
    Male
  • Location
    Lewis-Clark State College
  • Interests
    Ultralight flying and amateur radio.

Contact Methods

  • Website URL
    http://www.lcsc.edu/education

FileMaker Experience

  • Skill Level
    Intermediate
  • FM Application
    17

Platform Environment

  • OS Platform
    Mac
  • OS Version
    High Sierra

Recent Profile Visitors

545 profile views
  1. Thanks, as always, for your reply. I apologize for my poor explanation skills. To put it succinctly, I want to avoid using dozens of test-for-IsEmpty-and summary fields (per table, and there are fourteen tables), just to give a go-/no-go flags for reports to print. You're right in that e-SQL's out since it would be problemetic dealing with found sets. I just finished making a looping script but there's a big performance hit when it comes to thousands of records to plow through. However, it just occurred to me while writing this post that a "simple" solution would be an extension of what I posted earlier, to have just two fields per table: one that would be a calculation field with a litany of Case statements to test for each report's minimum field requirement, and the other a summary field of the calculated field. I could then use a very simple script to act as a switchboard to select which report to run based on a global field that has a drop-down menu of report titles; the aforementioned calculation field's result will be based on what's in the global field. Time to get coding!
  2. Greets, all: I have a dozens of print-related scripts but I want to use scripts--instead of using scores of hard-coded calculation and summary fields--to test for the presence of values within fields both in same table and parent-child table fields--so if not all the required fields for a particular printout have values, either in the current record or anywhere in the found set, it's flagged and another script notifies the user that none of the (found) records meet the required minimum field value requirement. Is there an elegant way to do this all in scripts or am I stuck using calculation and summary fields? ( The calculation field sets up the test with a result of 1 or 0 and the summary field sums the calculated fields--if the sum is zero the user is shown the error message. TIA for your help!
  3. I'm having similar problems with Adjust Window in v17 (Mac)—the layouts won't resize even with Adjust Window [Resize to Fit] entered in a resizing script mulitple times. It also acts flaky between user privileges, too--Admin, no problem, but any other privilege and it won't work correctly. I found a temporary way around the problem by creating a standalone script that has just one instruction: Adjust Window [Resize to Fit]. So, in the resizing scripts I have, I've replaced the instruction Adjust Window with Perform Script [Resize_to_Fit] and that works.
  4. Just a quick follow-up: From the parent table, can that calc be tweaked so it will detect if there's more than one of the same value in the child table? ...or a native FileMaker Pro calc which will detect of any of the children's records aren't unique per their relationship with the parent record? It could be a litmus test of "Are all values unique? True/False."
  5. Beauty! Thanks!! I have the FileMaker SQL guides but I'll have to find additional references to help with my SQL education; I never would've gotten the syntax right (now) not knowing about the missing parameter. Because JOB_KEYWORD_JOB is so long, I thought I'd use an alias of it, JKJ, once the calc was nailed down.
  6. Greets, all: I _thought_ this would be simple: signal users that the value they're inputting into a field--in a portal--is a dupe. (For the incredibly lazy who won't scroll through the portal records, first, to see if the value's already there.) I figure a counting function ought to do it--with a count of greater than one, that would set a message window fired by a script trigger. I know I'm close but for some reason I just can't nail it: The calc is in the child table, JOB_KEYWORD_JOB ; the value field to test is Keyword__lxt; the foreign key is _kflt__JobID. I figure I'd count those values with the same foreign keys and keyword and that would give me the answer I need, no? ExecuteSQL ( "SELECT COUNT ( Keyword__lxt ) FROM JOB_KEYWORD_JOB JKJ WHERE Keyword__lxt = ? AND \"_kflt__JobID\" = ? " ; "" ; "" ; Keyword__lxt ) ...but that doesn't work; I'm sure a minor tweak will fix it but I've run out of tweaks. : S Of course, I tend to make things more difficult than necessary so if there's an easier way to accomplish the same goal, I'd appreciate it! Ciao, Rich
  7. Thanks! Sounds like a plan. : )
  8. Many thanks, Steve! That will certainly come in use with any future reports--it's a keeper.
  9. Oops, just figured it out: Case ( Min ( PRAXIS_CHILD.FirstAttempt::TestDate__lxd ) = TestDate__lxd ; "First Attempt" ; "" ) I put the local table after MIN instead of the other T.O. *blush*
  10. (I'm sure this calc is here somewhere in the forum but I couldn't find it, so my apologies.) I have a solution that captures test codes and the dates students take those tests, but what I want to do is flag the earliest date a student took a specific test with the phrase, "First Attempt". I included a set of sample records for a specific student with this post. As you can see, there are three instances of TestCode 0061 but I want the flag to appear in the earliest-dated record, 07-25-2009. I figure it will require a separate T.O.- keyed on StudentID and TestCode--and that somehow it's a comparison of one-to-many, but that's about as far as I got; I tried using the MIN command but got nowhere, so if you could steer me down the right path, I'd appreciate it. Thanks! FirstAttempt.fmp12
  11. It appears to be working fine, but I don't follow about inserting a script step to replace Constant's content by one; where should I insert that? I discovered that I had to tweak the far right ends of the calculation formulas for Report_Pass__lcn and Report_Fail__lcn to null instead of zero: Case ( not IsEmpty ( TestScore__lxn ) and TestScore__lxn ≥ TestMinPassingScore__lcn ; TestScore__lxn ; "" ) If zero is used it throws the count off.
  12. *smh* I never would've thought of using another table with multi-keys. Brilliant! I added another T.O. (PRAXIS_CHILD_FAIL) that mirrors the one you created to obtain the % Below Passing scores. (If you'll private message me your e-mail address I'll send that coffee card.) What I'm having trouble wrapping my head around is the Constant field--I've used something similar to it before to tie T.O.s together but by using a calculated value of 1; the one in your fix is just an uncalculated number field, so how does that field "work"? In addition, I noticed that in the added T.O.s (with Constant as one of the keys), irrespective of whether I use a > or < sign with its connection to Report_Avg_Score_Pass__lxs (or Report_Avg_Score_Fail__lxs), it doesn't change the output's value.
  13. Here you go. The account name/password are both admin. Praxis2.fmp12.zip Included is the script to print the report--it's fired by the Report button on the PRAXIS_Child layout; a popover appears where you'll enter the dates in the global fields provided. (I included a screenshot of the typical date ranges we use; I've included records that fit within those shown ranges.) Solve this one and a coffee card awaits! : ) Cheers, Rich
  14. I'll export the data into a new file and will set up the calculations in it--since it's an encrypted file and has student records in it, you can't look at it as-is; I'll then post a link for its access this afternoon after I'm done attending a couple of upcoming meetings. Thank you VERY much for your ongoing help! Cheers, Rich
  15. It's a Summary field that averages the TestScore field.
×

Important Information

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