Robert L. Stewart
rl_stewart at highstream.net
Thu Jul 1 06:42:42 CDT 2004
Susan, Ok, I see what you mean. And here is how I handle such things. There are two methods. All of the "lookup" type data, in your example, the publisher, would be a drop down list in a combobox. So, you would either use the not in list event to be able to add it, or a button to the right of the combobox labeled "Add" that would open a data entry form to do the add. I have done it both ways. And, there are pros and cons for doing it both ways. The biggest con for the not in list event is that it makes it too easy for people to enter things with an incorrect spelling. Oh, and a third way is to not make any of your forms modal. That way your users can navigate through your menu system and add records into the lookup tables without a hassle. I use a form that allows them to select the lookup table they want to edit rather than individual menu items for each lookup table maintenance form. And, in all of my currently developed systems, this last method is the one I use. But, in the past, I have used all three. Robert At 05:46 PM 30/06/2004 -0400, Susan Harkins wrote: >If you are going to maintain the relationship, you ALWAYS enter the one side >before the many side. I do not understand what you mean by unnatural when >you said that entering the one before the many felt unnatural. Can I have >line items for an order without the order itself? Can I have a home address >for a person before I have the person? > >==========Back to the simple books database -- you're entering book >information -- certainly, entering the title, ISBN, etc. is something you >want to enter first -- but then Ack! The publisher for the book you're >entering isn't in the publishers table yet -- that sort of issue. It's >clearly a thinking order -- meaning, "books" are the item you're tracking, >not publishers -- publisher is just supportive information. For instance, on >a paper form, publisher might be way down the list -- certainly the book >title would be the first line -- see what I mean? So yes, often to enter the >one value -- and often there are many one values supporting a many record -- >seems unnatural. > >Susan H.