Using FMP 8.0, on Windows Xp Pro.

I'm designing a form that will list all the components needed to build
an object. The number of components will vary, based on the object's
requirements. I could use a portal to do the data entry of all the
necessary components.

But when a user prints the list/report, I want the section that lists
the components to expand or contract to list all/only the components
needed. I know this can be done if all the components were entered
into a single text field, but, that's not the way they will be entered.
And I want each component to be separated by a horizontal line, to
help the user distinguish one entry from another.

So I'm describing this as an expandable form, since I want it to retain
the look of a form when it's printed. Sorry for the redundancy. Of
course, the report would be printed on more than one page, so I'm
assuming the form would just keep printing onto page 2 without any
further instructions on my part. Thanks for your help!

Sorry about double-posting like that. Anyway, thanks Harry, for the
help.

It all makes sense, HOWEVER, I really need the report to have in it
some information from the Objects file. Will I have to create a
relationship in Components file, and "pull in" this infomation from the
Objects file?

I guess I'm really asking if a variable length portal can be displayed,
that is, can a portal itself shrink or expand, depending on the number
of records in it? If not, any plans for adding this to future
versions? Thank you.

In article <1165860707.832102.210890 (AT) 73g2000cwn (DOT) googlegroups.com>,
steved (AT) dakins (DOT) net wrote:

Although you can do it, portals weren't really designed for printing,
but are for on-screen use. It's simply easier and more flexible to
print from the child file (it gives more sorting options, better
control for Summary sections, etc.), and therefore don't need a
"variable length portal".

You can simply have a relationship back from the Components file /
table to the Objects file / table to retrieve any information you need
from the parent record. Depending on how the information needs to be
used, you can use Calcultaion fields in the Components file / table
that pull in up-to-date information via the relationship, or you can
simply put the related fields themselves on the layout or as a merge
field in a block of text.

It's anyone's guess what might or might not make it into future
versions of FileMaker. "Variable length portals" might make it to
FileMaker 9 or might not appear until FileMaker 376 or never.

Helpful Harry
Hopefully helping harassed humans happily handle handiwork hardships ;o)

that work?

Thanks,
Steve

that work?

Thanks,
Steve

In article <1166028249.611639.275640 (AT) 73g2000cwn (DOT) googlegroups.com>,
steved (AT) dakins (DOT) net wrote:

As you should know, for a normal field you can drag the "Field" label
from the side-toolbar onto a layout and then choose what field it is.
In that "choose a field" window you can change the pop-up menu at the
top to access relationships to the fields in other files / tables.


FileMaker also has the ability to use Merge Fields, just like in Word
mail merge document. These are fields that appear inside a text block,
and are often a better way to display information than using a normal
field and Sliding.

Simply use the Text tool to type up some text, then with the text
cursor positioned where you want field data displayed, choose "Merge
Field" from the "Insert" menu. You'll then get the same "choose a
field" window where you can pick a local field or one from a
relationship.

You'll end up with a text block that in Layout mode contains something
like "<<field name>>" or "<<relationship::fieldname>>". When in Browse
mode or printed these placeholders are replaced by the actual data of
those fields, and all the following text shuffles up to remove any
gaps.

You can not perform Finds with Merge fields or enter data into them -
they're strictly for display purposes.




Helpful Harry
Hopefully helping harassed humans happily handle handiwork hardships ;o)