The MenuSeq is the sequencing order of the menu items. The MenuName is what you use in your where clause in the popup menu to bring up the relevent items.
So it would always go: Where menuname = 'somemenuname' order by 'menuseq' ----- Original Message ----- From: "TOM HART" <[email protected]> To: "RBASE-L Mailing List" <[email protected]> Sent: Saturday, May 25, 2013 8:45 AM Subject: [RBASE-L] - Re: Primary key Mike, What I use is 4 different drop down menus in a form to enter inventory(much like the drop down for States), none of them hold much data, maybe 100 rows, but each hold completely different types of data. If I understand your table I could select the data to load in each drop down based on the "MenuSeq". This does seem like a great idea. I will look into this. Tom Hart ________________________________ From: Mike Byerley <[email protected]> To: RBASE-L Mailing List <[email protected]> Sent: Saturday, May 25, 2013 6:39 AM Subject: [RBASE-L] - Re: Primary key While you are at it, "numerous tables" strikes a chord with me as being unnecessary. I use a single table structure like: CREATE TABLE `MenuTable` + (`MenuName` TEXT (12) NOT NULL , + `MenuSeq` INTEGER NOT NULL , + `MenuText` TEXT (50) NOT NULL , + `ReturnValue` TEXT (16) NOT NULL ) COMMENT ON TABLE `MenuTable` IS + 'S - Various Menu TEXT and Return Values' You can see it is not indexed at all as it only contains a few hundred rows, but if it ever became noticibly sluggish, I would put an index on the menuname. MenuSeq was added after a year or so, when I wanted something at the top selection that OrderBy wouldn't provide. All return values are TEXT, and when the result needs to be otherwise, the values are converted at runtime. ----- Original Message ----- From: "TOM HART" <[email protected]> To: "RBASE-L Mailing List" <[email protected]> Sent: Friday, May 24, 2013 11:10 PM Subject: [RBASE-L] - Primary key I am in the process of redoing my database that I've used for over 10 years, just trying to use logic in naming, correct syntax, etc. I have numerous tables that hold data to use to fill fields from popup menus and just wanted to know if it is better to set the field as a PK or unique, they do not reference other tables so there are no foreign keys. Is one way better that the other, just curious Tom Hart
