You mean like great minds think alike and fools seldom differ? Another reason for using this sort of thing is that it can easily be transferred to new databases so you keep some sort of consistency.
Regards, Alastair. ----- Original Message ----- From: "MikeB" <[EMAIL PROTECTED]> To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> Sent: Monday, June 14, 2004 11:03 PM Subject: [RBASE-L] - Re: Combo Box Values > > ----- Original Message ----- > From: "Patrick Murphy" <[EMAIL PROTECTED]> > To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> > Sent: Monday, June 14, 2004 4:28 PM > Subject: [RBASE-L] - Re: Combo Box Values > > > > Thanks Alastair, Emmitt and Jim: > > > > I am currently using a table for these items, with a single different column > > for each combo box selection, i.e. Mailing Address Code (1-6), Salutations, > > Relationship of Child to Parent, Relationship of Parents to Member, and > > Employment Status. > > > > This works, but Alastair's is more interesting and sophisticated, and avoids > > the problem of having to add a new column when a new such requirement comes > > up. > > > > Thanks to all! > > > > Patrick > > > > >There are other ways, Patrick, but I doubt any of them are any easier. > > > > >Using a table if you need to add another title - to use your examples, say > > "Dr." - all you need to do is add a row. If you try and do some >fancy > > coding you're probably going to have to edit the code each time. > > > > >What I use is a single table for all my "low number of rows" menus with > > these columns: > > > > >Menu_Type - to give me the particular rows > > >Menu_Sort - to allow a sort other than on the next two columns > > >Menu_Description - what appears on the menu > > >Menu_Returned - what goes into the table via the form > > Emmit, > Isn't it funny when the solution someone else comes up with is like your > own... My MenuTable > Table: MenuTable No Lock(s) > Descr: -0- > > No. Column Name Attributes > --- ------------------ -------------------------------------------------- ---- > 1 MenuName Type : TEXT 12 NOT NULL > 2 MenuSeq Type : INTEGER NOT NULL > 3 MenuText Type : TEXT 50 NOT NULL > 4 RetVal Type : TEXT 16 NOT NULL > > > > > >You could argue that they should be different tables for each Menu_Type but > > this works for me. > > > > >Regards, > > >Alastair. > > >
