|
I see. The instructions regarding "columns
not on this form" do not apply here, because the add form can only show columns
from the current table. What you're looking for is a way to make the
AreaID field a filtered select.
Make sure the Area table has an alternate key
specified, and that its primary key consists of a single column. Then you
should be able to change that field to be a filtered select menu.
HTH,
Dave
----- Original Message -----
Sent: Friday, January 07, 2005 11:12
AM
Subject: Re: [plum] Filtered Select Lists
and IDs
This occurred on the Model Add Form. I
want the filtered select because I will not know which Areas are available.
The Pay Grades are static, so I guess that I could enter an enumerated value
set there, but if I already have the key-value pairs in the DB, that is an
extra step.
Sender: [EMAIL PROTECTED]
Reply-To:
[email protected]
X-Rcpt-To:
<[EMAIL PROTECTED]>
Marwan,
On which form is this problem occurring?
Also, are you trying to use filtered select menus, or are you wanting to
display static values on the form?
Dave
-----
Original Message -----
Sent:
Friday, January 07, 2005 10:24 AM
Subject:
[plum] Filtered Select Lists and IDs
I have a table Models which
includes the columns AreaID (an FK pointing back to the Areas Table),
LowerPG (FK to the Pay Grade table) and UpperPG (another FK from Pay Grade).
In the Plum IDE, the database info shows me my parent table relationships to
the Models table, but when I generate forms, they automatically use the
AreaID and PayGradeID (ints) rather than the Text label associated with
each. This is expected, but in the tutorials it shows the parent items in
the “columns not on this form” and suggests to swap out the ID column with
the name column. However, those parent form columns are not in my form
choosers. Does this make sense? What am I doing wrong? Thanks
Marwan
Saidi
American Eagle Information
Systems
321.779.2577 -
p
321.779.2576 -
f
|
