Hi Tim,
It seems to me that you would want to normalize your database, so I would go with separate tables. Using Plum shouldn't
influence db design issues, IMO.
On the question of the forms, are you planning on putting 2 select menus on one form, or on two separate forms
(ManufacturerAddForm, ModelAddform) for instance?
cf_FilteredSelect doesn't support chaining like that at this time, although I asked for it. Maybe Adam and David will
consider it for v 1.1. If you are going for the former option, you will have to do something like use Nate Weiss'
CF_TwoSelectsRelated tag, bracketed between a <cf_DisplayExtraFormContent> tag pair. I did this on a project last year,
and had to use custom queries to drive it. qForms supports populating multiple selects, also, so that is another
option. But no native way in Plum to popluate one select dymanically from another at this point.
HTH,
Jeff
Tim Blankenship wrote:
Alright I know I should be ashamed, well I am, I need a little help.
What I want to do is have a form that lists some info on server
hardware that has a filtered select list on it.Basically I want to
choose a manufacturer (HP, IBM, Dell...) and when I choose the
manufacturer the Models are populated for the specific Manufacturer.
Example I choose HP in a select menu the next select menu is populated
with Proliant 123, Proliant 234, Proliant 345. So inturn what is the
best method for the DB design, a single table like
ID, man_ID, manufacturer, mod_id, model
or should I split them
Manufacturer table
man_id, manufacturer
Model table
mod_id, model, man_id
I know this is somewhat simple but I am just having a brainfart this morning.
For testing and client approval I am making it in Access but
eventually I will recreate this in Oracle.
**********************************************************************
You can subscribe to and unsubscribe from lists, and you can change
your subscriptions between normal and digest modes here:
http://www.productivityenhancement.com/support/DiscussionListsForm.cfm
**********************************************************************
