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
> >>
> > 
> > 
> > 
> 

Reply via email to