Hi,

In FMP 8.5 I created a solution with following tables:
- products
- purchases
- purchase line items

If I have a new product that is purchased, I first create it in products
and than I turn back to the purchase table.

When I have lots of new products this is a lot of work and means
switching a lot back and forth (between products and purchases).

Now my question: is it possible from within the purchases table that new
products are created automatically (in the products table)?

Thanks for all help.
Hans

On 05/04/2007 12:41:58 hpuype (AT) gmail (DOT) com (Hans Puype) wrote:

Assuming there is a relationship between Products and Purchases, place a portal to the Purchase table on a Products layout. Include whatever fields you want to see. Make sure the relationship is defined to allow creation of records in Purchases through the relationship.

Matt

"Matt Wills" <I'm (AT) witz (DOT) end> schreef in bericht
news:541459.WFEURVJX (AT) news (DOT) verizon.net...
Be aware that this portal might not be a filtered portal, or you might
'loose' (at least visualy) the record the moment you tab out of the portal.
Whatever you do you still need to add it twice. once in the portal and then
connect it to the current record. IMHO the rule is simple: don't turn on
Allow Creation of Related Records and don't allow users to enter and edit
fields directly in a portal unless no other reasonable options are
available. This no doubt comes as a shock, especially in light of the fact
that FileMaker seems to lend itself so well to doing just the opposite. In
fact, FMI tells you directly to allow creation and editing of records in
portals, but don't. In general, a portal that allows creation of related
records or editing in the portal simply looks and feels amateurish. It can
also sometimes lead to problems such as orphaned or empty records. Think of
portals as tools for record viewing, selection and navigation, not for
editing or printing. How then are you supposed to create portal records?
Create an additional relationship to the table in question. Make it a
one-to-one relationship using a global field as the primary key and the
existing ID of the related record as the foreign key. Put (global)fields
from that relationship on a platform on the layout, along with a New Record
button. Attach this button to a script that creates a new record in the
related table, grabs the ID number of the new record and inserts it into the
new global primary key field. Also put a button over the portal row that
sets the global primary key field to that record's ID number, so that
existing portal records may be edited in the fields on the platform. You'll
have to make certain your scripts empty this global field when you change
records in the primary table. If you freeze the window during the script you
won't see what is happening.

Keep well, Ursus