|
From: Bruce & B. R. <br...@dc...> - 2021-01-26 23:40:51
|
Good morning David, Thanks for the clarification. May I suggest that instead of using radio buttons, you use an associated list selection that is defined by the parent classification. So create internal tables so that your main selection table is a table of tables (or lists) with the key field being your parent selection and your subsidiary selections being either a list of selections or further tables. In my experience, using radio buttons in this way tends to become very complicated and very fixed in form. On the surface it appears to be fairly simple in concept but when trying to actually develop a useful tool, it often becomes mired in complexity. I was originally introduced to the idea of "tables of tables" from a project going back to about 1986 and have successfully used in many times in many different projects since then. If you want to discuss further, feel free to contact me directly. regards and blessings Bruce Rennie On 27/1/21 3:50 am, David Gamey wrote: > Bruce, > > It's pretty simple. I have a source of short descriptions and URLs I > want to walk through. > > I may want to modify the description. > > I also want a control that will let me basically file the text pair in > a category. Say a radio button ... A, B, C. > > I also want a control that will let me further classify it. The > further classifications will be different. So A and A1/A2/A3, B and > B1/B2, etc. > > There are some other embellishments that will likely evolve but that > is the most basic. > > Finally something I don't want to do via command line :) > > Thanks > David > |