FM 8.5

I am trying to create a 'shipping cost estimating' solution but I am
having difficulty getting my portal to create new records. The main
variables are the 'ship to location' and the 'dimension of the
shipment'.

There are three tables; SHIPPING RATES (rates based on a Port_ID for
the city), LINES SHIPPING and PRODUCT SHIPPING (dimensions based on
style name). My layout table is SHIPPING RATES.

Now I want to insert a portal into my layout wherein I can create an
order of styles and quantities. This will produce a Gross shipping
voulme in CuM. When I do this I cannot get my portal to generate more
than one record. I have 'allow' for create records through these
relationship toggled on. Any thoughts why?

Another peculiarity is that when I change the Port ID my one portal
record disappears. Again, any thoughts why?

Thank you
Matthew

On 2010-07-26 14:24:33 -0700, Buckbuck <buck.matthew74 (AT) yahoo (DOT) com> said:

When you run into these kinds of difficulties, always look at the data
in the key fields for the relationship. Just having the create records
checkbox checked isn't enough.

The parent record must have valid data in the key field, and must have
been committed. In other words, after the parent is created, click
outside the fields and commit. If you create the parent, then
immediately go into a portal row & start trying to create records,
those child records will go into the ether, not having valid data in
the key field.

Parent key must have UNIQUE data. If you're using a field with
duplicate data that is in another parent, the child records will link
to the first created parent record with that data.

The child key field must be able to accept data. It's best if both
sides are the same field type (text or number).

I always find it useful when debugging to put those key fields on the
layout, temporarily. Seeing the data is always useful.

Make sure the fields in the portal are within the first row. If they
are not, you get the "one row" phenomenon. Also, make sure they are
from the same relationship as the portal. If you've duplicated another
portal, then changed the relationship on the portal, you must change
each field as well. They don't auto-change. This will give you the
disappearing record whenever you commit.

Try those steps, see if the problem is fixed.
--
Lynn Allen
--
www.semiotics.com
Member FBA
FM 10 Certified Developer