Hi Guys,

I need a little help. I have two tables A and B. The tables are linked
using the X relationship. Table A is a preferences type table, with
only one record. I have a layout which show Table A, and I have a
portal showing table B. In addition to the portal, I have other fields
that are part of Table B. When on the layout, I see all the records in
Table B on the portal, but when I click on the various lines on the
portal, those other Table B fields do not change to show the current
record selected on the portal.

Is there a way to do this? I want to be able to edit these fields on
this layout. My Table B is a Name, Address, Phone type table. I know I
can do this on separate layouts, but the application would greatly
benefit from having this information in a consice place.

I have read the FM Bible book cover to cover, and the help file. I do
not seem to be able to figure this one out.

Any help is greatly appreciated.

Thanks,
Nando

BTW. FM 8 Pro is nice (from my newbie perspective). The tabs feature
alone is worth the uprade.

In article <4cffh1hmj1gmn96m6qnnesvvk40kbg9of9 (AT) 4ax (DOT) com>, not (AT) now (DOT) com
says...
Make a self-join from A to A (type X)
Use that as your portal. Overlay an invisible button (ie draw a
rectangle with no border set to transparent over the uppermost portal
row, assign to go to related record.

If you need to show records from your B table, use the existing
relationship since its only one record just add the related fields to
the layout.

-regards,
Dave

It is a real plus. $200.00 per user for tabs alone is NOT worth the
upgrade price though.

On Fri, 02 Sep 2005 04:29:37 GMT, 42 <nospam (AT) nospam (DOT) com> wrote:

Thanks dave. I tried what you suggested without any luck Please see
what I tried below.

I created the A to A relationship. When I assigned it to go get
related record from Table B. I get an error message that "it cannot
display the result"

When I assign it to get records from Table A2 (the new X relationship,
I still have an A to B X relationship), the B fields in the layout do
not change as I go record to record on the portal.

If I setup the portal to show related records form A2, the portal only
show the first item in Table B.

Thanks again.

In article <4cffh1hmj1gmn96m6qnnesvvk40kbg9of9 (AT) 4ax (DOT) com>,
Nando <not (AT) now (DOT) com> wrote:

Maybe I don't understand what you are trying to do, but I don't think it
can be made to work as you describe it.

Selecting a record in a portal does just that. It does nothing to change
what records are displayed outside the portal, even though those records
are from the same table as inside the portal.

You can edit data in records inside the portal, as long as the fields
you want to edit are displayed in the portal and are formatted to allow
access in the Browse mode.

You can also create new related records in the portal if the
relationship is set up to allow creation of records.

I do not understand the purpose of Table A, with only one record. What
does that do for you?

Perhaps if you tell us the overall goal of what you are trying to
accomplish with your solution we can help find a good way to do it.

Bill Collins

--
For email, remove invalid.

Thanks Bill,

I have a table to store Preferences (table A). This is not where my
main data is stored. It only has one record because this is where a
user would store a single set of settings that would be read within
the main table. I select and store things like measurement units (feet
or meters) . On this Preferences table and Layout, I want the user to
be able to edit items from another table (table B) which is called
upon for drop down lists. I don't want to have separate layouts for
editing every table on these lists, and the logical thing would be to
bundle everything in the Preferences layout.

Thanks again.

In article <5aogh19035fm667hosckklbqfop4s1is1t (AT) 4ax (DOT) com>,
Maker Fan <reef (AT) home (DOT) com> wrote:

OK.

I think you need a portal to Table B located in the layout of Table A
that the user will use. In the portal, display the Table B fields you
need to have the user enter and edit data. Create and edit records of
Table B in that portal. That should take care of your needs. Define the
appropriate fields in Table B to take values by lookup or calculation
from Table A when the Table B record is created.

But then again, I think you could also just use Table B alone, and have
value lists to select from to take care of filling in what you are now
calling Preferences. Without knowing more detail about your overall
goals, that approach would seem preferable to me.

Bill

--
For email, remove invalid.

Are you saying your in a layout in Table A and showing records from
Table B in a portal. That you also have fields from Table B on the
above mentioned layout but NOT in the portal. Now you want the fields
from Table B (that are not in the portal) to show the data from the
record that you clicked on in the portal.

If that's the case, you'll have to do the following:
- create a global number field in Table A
- create a relationship from Table A::global number to Table B::unique
ID
- put a button in the portal that runs a script which sets the global
to the unique ID, Commit the record (DON'T skip this step)

Hi FP,

Thanks for the info. What you described is exactly what I am trying to
do. In essence I want to see ALL the records of Table B in the portal,
and when clicking on any one item, I can edit that item's data on the
fields that are NOT in the portal. So the portal acts as a record
selector list. I don't think I was not clear enough about how this
part was meant to work. I have container fields and long address
fields that would look quite cumbersome inside of the portal.

I gave what you suggested a try, but I think it's missing something
because when I go into the layout for Table A, the Portal B shows no
records if the related fields are blank, or it will only show one
record when the two fields match.

I really appreciate everyone's attention to this.




On 2 Sep 2005 13:05:35 -0700, "FP" <a (AT) pottnerconsulting (DOT) ca> wrote:

You need 2 separate relationships here.
In the relationship graph create another occurrence of table B and call
it "A_B All Records". Create a relationship from table A to the new
table occurrence using any fields but use the cartesian product (X)
instead of equals.
Add another occurrence of table B and call it "A_B Global XX Unique
ID". Create a relationship from table A to this table occurrence
linking the global in A to the Unique ID in B and using equals
(default) for the relationship.

In your layout in table A, the portal should be using table occurrence
"A_B All Records".
The fields that your displaying from table B eg. Address etc. should be
using the table occurrence "A_B Global XX Unique ID".
The button that needs to go into the portal should run a script which
sets the global to "A_B All Records::Unique ID" then commits the
record. Once that has happened your fields like address should show
the data from the record you've clicked on.

Simple genius!! It worked like a charm. Thank you very much. You guys
are the best!!



On 2 Sep 2005 22:59:29 -0700, "FP" <a (AT) pottnerconsulting (DOT) ca> wrote: