> Correct me if I'm wrong.. when you say orphans you are meaning basically > any row that would be in the TimeTable that for some reason the parent got > deleted.
Sorry, not a very technical term. I just meant any relationship that is missing one or more links > I know we have had a few headaches when our plant manager, and stock > control person have complained about not having a good way to tell if when > looking up certain parts as to whether a job is started or not.. So you're thinking as soon as time is logged the job has started? If true, that's a great idea. > This is my > ultimate goal in all this. This leads me to believe that It would be better to > create a routine for removing/deleting jobs that would get rid of the info in > both tables-- as it should be. I do wonder, how would one go about keeping > someone from deleting a row in the parent thru the form? Thinking...ouch PK/FK should work. Or use a Button [Delete] and flag rows for deletion from the eep. I don't use form menus and don't tell my clients about [F9]. > Please bear in mind, I did not design this db.. My Boss did, and overall it has > served the business well, it's just needs to be tweeked to serve some more > specific and detailed needs. Most of our db's are DOS 6.5++ including this one. The design doesn't look bad (at least these two tables)... I think it's just a matter of how you want to implement it. Ben Petersen > Ben Petersen wrote: > > No. Wouldn't bomb, just wouldn't be included in the view. Maybe that's not an > > issue? I could imagine routines failing if they expected a correlation and > > didn't find it. Although you started wanting to know if there were any > > orphans. > > > > It's more of a user friendly issue. If you use multi-table forms you have to > > train users to access the second table before exiting, if you use "enter > > using", to satisfy a PK/FK constraint (the other way to avoid orphans). You > > also have to decide if the same form is satisfactory to both edit and enter... > > or maintain two forms. > > > > If you code so as to always have keyed, empty rows available, and to > > present "left-over" empty rows when the user wants a new record, everything > > becomes very predictable and more easily managed. > > > > I use the same logic to force completion... if the user wants to "add new" > > they keep getting the last incomplete record until the entry is properly > > completed or deleted. User friendly, fewer rules, fewer forms, less > > training... > > > > Ben Petersen > > > > > > > > On 19 Mar 2003, at 16:18, Jim Limburg wrote: > > > > > >>Hey Ben > >> > >>That sound feasible, but... I was just thinking.. the hours > >>are not recorded until there are hours, so what would happen > >>in this if there is no mponums in the TimeTable table? > >>It wouldn't bomb would it? > >> > >>Attempting to come to life > >>Jim Limburg > >> > >>Ben Petersen wrote: > >> > >>>Hi Jim, > >>> > >>>>From the view, or either table, you could could test for null in one or more > >>>> > >>>columns: > >>> > >>>Sel * from HdrTable t1, TimeTable t2 + > >>> whe t1.MpoNum = t2.MpoNum and + > >>> t2.WorkHrs is Null and t1.ItemNum is Null > >>> > >>>Ben Petersen > >>> > >>> > >>> > >>>On 19 Mar 2003, at 15:51, Jim Limburg wrote: > >>> > >>> > >>> > >>>>G-Day all > >>>> > >>>>I would like some advice. > >>>> > >>>>We have one table which is basically a header table for MPO to track > >>>>jobs in the plant.. then another table that gets data from timeclocks > >>>>for each Mpo number and related data.. > >>>> > >>>>I want a view and ultimatley a report that I would run on this view to > >>>>show all the mpos that do not have time put onto them. In other words > >>>>Mpos entered into the system, but not yet started on.. > >>>> > >>>>General info in the header table I would like to collect would be > >>>>Mponum, Itemnum, ShrtDesc,QtyOrd,Location,shopordr > >>>> > >>>>and then the table of time tracking we have > >>>>Mponum,WrkDate,WorkHrs,OTHrs,DTHrs,ClockNo > >>>> > >>>>Can someone give some suggestions to break this fog I'm in.. > >>>> > >>>>I know this is so simple it's going to make me kick my can when I see it, > >>>>but I've had one of those head in the cloud days.. > >>>> > >>>>Thanks for input > >>>>Jim Limburg > >>>> > >>> > >>> > >>> > > > > >
