Steve Martino

High praise indeed...Thanks Lee

Was much easier after Lee created the file, and you provided some data-saves everyone time. I received tons of help on these forums, always trying to return the favors.

Sample files help... Should be right, (bone-head mistake on the calc by me) complicated calculationSMmod.fmp12

Ah...so maybe: Let([ @gr=P1_Rounded; @param= Case(Conduct="U" or ISS="ISS" or academic_integrity="AI";"N";"E"); //----------If they meet this criteria, return "N"-------------- @test= Case(@gr ≥ 95 and P1_Absence ≤ 3 and P1_Tardy ≤ 3;"E";"N"; @gr ≥ 90 and P1_Absence ≤ 2 and P1_Tardy ≤ 2;"E";"N"; @gr ≥ 70 and P1_Absence ≤ 1 and P1_Tardy ≤ 1;"E";"N"); //----------If they meet this criteria, return "E"-------------- @exempt=Case(@param="E" and @test="E";"Exempt"; "Non-Exempt") //----------If they meet both critera, return "Exempt"-------------- ]; @exempt )

It's kinda of a trial and error thing. I use an LQ590. I had to create a custom paper size, a little smaller than the actual size I'm printing on. Then look at your layout in layout mode, show margins, and make sure nothing is extending past the margins. Oddly, the tickets printing I print are 11" wide and 5" tall, but I still had to select 'Portrait' for them to print correctly. When I switched from 12 to 16 I had problems printing. When I put both DB layouts side by side in layout mode, showing margins, the margins were the problem. I even copy/pasted the exact layout from one DB to the other, and still had to adjust the margins to get it to work.

Try this, again, can't test: Let([ @gr=P1_Rounded; @param= Case(Conduct="U" or ISS="ISS" or academic_integrity="AI";"E";"N"); //----------If they meet this criteria, return "E"-------------- @test= Case(@gr ≥ 95 and P1_Absence ≤ 3 and P1_Tardy ≤ 3;"E";"N"; @gr ≥ 90 and P1_Absence ≤ 2 and P1_Tardy ≤ 2;"E";"N"; @gr ≥ 70 and P1_Absence ≤ 1 and P1_Tardy ≤ 1;"E";"N"); //----------If they meet this criteria, return "E"-------------- @exempt=Case(@param="E" and @test="E";"Exempt"; "Non-Exempt") //----------If they meet both critera, return "Exempt"-------------- ]; @exempt )

So to make it a little clearer for 90-94, the student must have: -Average grade between 90 and 94 -Must have less than or equal to 3 Absence AND 3 Tardy -AND- Must have Conduct=U OR ISS="ISS" OR academic_integrity="AI" Am I on the right track? Seems like Conduct, ISS or academic_integrity are all must haves for Exempt, regardless of grade...correct? Let me know

Then why do you have both 9 and 09? If they are just numbers, then: Let([ @name=left last name; @grade=Grade Level; @Con1=Case(@name ≥ "A" and @name ≤ "E"; "Counselor1"; @name ≤ "Le"; "Counselor2"; @name ≤ "Rh"; "Counselor3"; "Counselor4"); @Con2=Case(@name ≥ "A" and @name < "L"; "Counselor 5";"Counselor 6"); @Con=Case(@grade>8;@Con1;@Con2) ]; @Con )

This way may be more accurate: Let([ @name=left last name; @grade=Case(Grade Level="09" or Grade Level="10" or Grade Level="11" or Grade Level="12" or Grade Level="9"; 1;2);//determine which group @Con1=Case(@name ≥ "A" and @name ≤ "E"; "Counselor1"; @name ≤ "Le"; "Counselor2"; @name ≤ "Rh"; "Counselor3"; "Counselor4"); @Con2=Case(@name ≥ "A" and @name < "L"; "Counselor 5";"Counselor 6"); @Con=Case(@grade=1;@Con1;@Con2) ]; @Con )

A couple of potential issues I see is the use of "06" and "6". Are these text fields? A little nervous about have fields like that. Also, you shouldn't have field names with spaces, for many reasons... Try this in data viewer (can't test without a file), you'll have to change left last name to a full reference of YourTable::left last name. Same for Grade Level. Let([ @name=left last name; @grade=Case(Grade Level="09" or Grade Level="10" or Grade Level="11" or Grade Level="12" or Grade Level="9"; 1;2);//determine which group @Con1=Case(@name ≥ "A" and @name ≤ "E"; "Counselor1"; @name ≥ "F" and @name ≤ "Le"; "Counselor2"; @name ≥ "Li" and @name ≤ "Rh"; "Counselor3"; "Counselor4"); @Con2=Case(@name ≥ "A" and @name < "L"; "Counselor 5";"Counselor 6"); @Con=Case(@grade=1;@Con1;@Con2) ]; @Con ) Edit: Fixed typos.

I would say you could treat it like an invoice. Add a join table (LineItems). Make LineItems a Prescription. Patient-------<Invoice>-------<Prescription>--------Product Then a Patient layout can have a portal of all the Invoices. The cost can then be looked up from product or a calculation. Here's an old sample file u/n: admin p/w: 1234 Navigate to: -Products, to see Product info, and to change prices. -Customers, to see customer info and related Invoices. -Invoices, to see how to create an invoice, picking from a portal. I didn't have time to strip out everything not needed, but maybe when I have some time. This should give you the gist of the relationships, scripts and process. InvoiceSM.fmp12

Lines 56-69 <TH SCOPE="ROW"><div class="hidden">Information</div></TH> <TD NOWRAP="nowrap"><input id="1" type="radio" name="query_param" value="USDOT" checked> <LABEL for="1">USDOT Number</LABEL></TD> <TD NOWRAP="nowrap"><input id="2" type="radio" name="query_param" value="MC_MX" > <LABEL for="2">MC/MX Number</LABEL></TD> <TD NOWRAP="nowrap"><input id="3" type="radio" name="query_param" value="NAME" You'll need to move 'checked' to after "MC_MX to have 'MC_MX' checked as default, then you can put your number into the search box.

If I follow correctly, you want to take a value in your database and put it in the form on the website?

Case( get(currentdate)>YourTable::DueDate field; YourTable::BalanceField * .1 ) But it seems like you are creating a separate record for a late charge. This may actually be a better way IF in the following month you take the current balance, and apply 10% to that (like a credit card).

+1 I honestly didn't know that was a real cat for about a year...don't know much about cats and never saw one like that.