dwins

Poor man's popup. This can also be done with one calculation field and one script. The calc field generates the next 52 Sunday dates from the current date forward, each separated by a return. The script takes the value in that field where the cursor resides and places that value in another field. I have a publication that runs on Thursdays. To set date for an ad or subscription you click on the date field, a button. If date field is empty, a list of dates appears, click on your choice, click date field again, the date is set. If date field is not empty, it is selected for editing.

Your're forgetting to not listen to novices like me. Go back to Rod's or Jeeps suggestion. I thought I could help as I do this regularly with other field types and thought I had done it also with containers but evidently not. Sorry.

A script can extract, or act on, a particular value, where the cursor is placed in a block of text.

Stack the containers on top of each other, make them unenterable, hide them under a rectangle object that can form the background of your other fields, buttons, etc. You then enter each container with a script thus bringing it to the fore displaying its content.

JPEG, PICT print good for me - TIFF, PDF do not.

I would take Fitch's suggestion a step further and have one view/print page to a layout - 15 layouts. Nothing faster than clicking from page to page, nothing slower than trying to scroll around when it's spread over 110 inches. And you design where the page breaks are, etc. However, if you're dead set on one layout you could miniaturize everything then set your Page Setup to 150, or whatever, percent.

This doesn't address SimpleChart. But the graph you want is only four points. Note that if a bar graph would be suitable, one can be made easily with a calculation field. Let ( a = "llllllllllllllllllllllllllllllllllllllllllllllllll" ; Left ( a ; 300mV ) &¶& Left ( a ; 5V ) &¶& Left ( a ; 7V ) &¶& Left ( a ; 10V ) ) Depending on font, a lower "L", or any character, can be used, field can be rotated, and about 3 or 4 stacked should make bars solid. Among variations: Multiple bar graphs can be stacked, a chart can be made of multiple records. A point chart can be made using spaces &"•". A curve can be made by tightly spacing many points. A line graph can be made by adding formulas between your results that break the difference into equal parts. You'd need lots to make the line smooth. I've not done this one myself, but one calculation is cheaper than a plugin. Of course how this displays depends on the font so you want to be careful if it goes on different computers.

Base the value list on a calculation field. Case ( completed = "Open" ; name )

or: number * .01 * ( 100 - GetAsNumber ( popup ) )

A similar problem solved by the Fenton #2. 100 businesses that sponsor an ad are all billed at once. Scrip, here shortened, creates one ORDER for each ACCOUNT (child and parent). Go to Layout ORDERS Show All Records Show Omitted Only //this hides all records so in the end you view only the new ones Go to Layout ACCOUNTS Perform Find //to get the 100 parent records you need. Go to Record First Loop Set Field gHolder;Pkey //you'd use variable here Go to Layout ORDERS New Record Set Field Fkey;gHolder Set Fields with the data you want on the record Go to Layout ACCOUNTS Go to Record Next Exit after last End Loop Go to Layout ORDERS Data for the records is held in proxie globals. Accounts to be Billed are checked "X," then changed to "B" in the Loop. For safety the script will exit if it hits a B. B's are kept for further script action then cleared with a button.

This formula rounds positive numbers up. Let ( [ a = 234.000003 ; //number b = 2 ; //decimal places c = 1/10^b ] ; Ceiling ( a / c ) * c ) //gives 234.01

A question you might ask is if there's a way set the data in the first place using a script. Then that script can also do anything else. For example, if Plated / Printed is chosen from a popup, then instead you could use a script that scrolls, or toggles, through the choices. Or you could make something, like a radio button field, where you see all the choices, but make your own script buttons to mark the choice.

You can format the popup field text to whatever color you like for viewing the popup list. Then use an auto-enter calculation, TextColor( ), to make the text your desired display color.

Here's an answer I don't recommend. This reminds me of a gadget I've used: an entry in fieldA causes a response in fieldB. Likewise an entry in fieldB causes a response in FieldA. This requires at least three fields. This usually works in one direction and not the other because of reasons Soren gave. So stack a calculation field on top of the side that's not working - and, there are other variations to make this work smooth, but... That said, for your purpose, please DON'T have any mechanism whereby a content in one critical field deletes the content of another. You can have them mutually exclusive where one field stays empty if the other has content. That's easy with autoenters. But try to make the layout so if the cat runs over the keyboard you're not screwed. Also consider the terms: the opposite of debit is credit - the opposite of deposit is withdraw. That reminds me of Gibson guitars which for over 50 years have had a label on the pickup selector switch: RHYTHM / TREBLE (Although actually those terms do equate only in the fact that neither equates to pickup selection.).

FileMaker sans plugin, no. But you can go from the two clicks of exiting the field to one click or less. So as you type in field A, hit shortcut key or button to check length, your cursor never leaves the field. Make field B a button, the script of which updates the Length, and make the last step Set Selection to put the cursor back in Field A.

Or just go to a New Window to view detail

You need to OMIT all records except the one you're viewing. Show All Records Omit Record Show Omitted. Add that to your details-viewer script. GTRR works if you're going between related tables, you can choose to show only the parent record or view only the children.

You could make field A a text field and make it non-enterable. Make it a button, use the Set Selection or GoTo Field script to enter the field if field B criteria is met. Else script copies or transfers field A content or whatever, etc. Freeze Window If [field B says bla bla] Set Selection [field A] Else Copy [field A] End If

Not just what you ask, but - You could have a button that you click to get the score. If you end the script with Set Selection the cursor never leaves the field - one click - the user won't miss a beat. It's at least smoother than clicking out to commit the field then clicking back in. And the user may not need to use it as you'll have the field sized about right (Courier?). And just in case, an auto enter calc cuts it off at 30 characters. Don't forget the TrimAll.

Use the Set Selection as the LAST step in scrip and just indicate the target field, no other parameter necessary. so: Set Field [popup; "" ] clears it Set Selection [popup] selects it One click effects the above script, and since the field is now selected, the second click opens the popup.

The field itself could be a button which clears itself and remains selected for the popup. So, first click clears it, second click pops it open. Set Field [popup; "" ] Set Selection [popup]

You can use the Pause/Resume script to help make words blink, or run a clock and other things. But the problem is as long the word blinks the script is running and so your database is on hold until you stop it. Maybe you can modify this to fit your purpose: Allow User Abort [On] Loop Set Field [field;"DOG"] Pause/Resume Script [.5 sec] Set Field [field;""] Pause/Resume Script [.5 sec] End Loop

Evaluate ( Substitute ( fieldname ; ¶ ; "+" ) )

Comment posted ahead of me. So I'll say it this way. I don't see anything in your plan that would not be solved by simply putting all your displayed fields on the header, and just have the name field(s) on a one-line body. You'll have the expanded info of the selected record displayed at the top, and your found set listed below. No portals, no self-joins needed. If you want a separate "start" page with the search fields, that's just another layout.

You could string everything in a calc. quote_description_1 & Case ( not IsEmpty ( quote_description_2 ) ; ¶ & quote_description_2 ) & Case ( not IsEmpty ( quote_size_1 ) ; ¶ & quote_size_1 ) & Case ( not IsEmpty ( quote_size_2 ); ¶ & quote_size_2 ) & Case ( not IsEmpty ( quote_amount_1 ); ¶ & quote_amount_1 ) & Case ( not IsEmpty ( quote_amount_2 ); ¶ & quote_amount_2 )