Sorry Jim, I didn't get that, but Dennis did. You might consider coding in such a way as to not allow orphans. If people are working from the R> this could be tough, but if you're writing an app, insert a common key to both tables. For the next time entry, check for an unused row and edit it - or - do another insert and then edit. Saves tones of grief.
Ben Petersen On 19 Mar 2003, at 16:20, Jim Limburg wrote: > I hope I made myself clear on the last post. > Basically I was thinking.. What if there we no records > in the Timetable table so there would be way to compare > mponum to mponum... > > Jim > > 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 > >> > > > > > > >
