MarkShnier__You
Qrew Legend
Qrew LegendRe: Using date ranges across multiple tables
Louis
I do know how to do this.
My thought is that when a user views a Discrepancy, the form will take data from the Discrepancy Table (Discrepancy #, Machine #, and Discrepancy Date) and will display all Parts where Discrepancy Date falls between Part Installed Date and Part Removed Date, and Discrepancy Machine # equals Part Installed On Machine # . So the User will be given a list of all parts that were on that machine on that date, and they can choose the correct part.
I can help you one on one to implement a solution, but here would be the proposed workflow it this meets your need.
The user views a Discrepancy and on that record click a button. The button will edit or add to a table of users called User Focus table where the key field is the Userids. The particulars of the Descrepancy record will looked up by a reverse relationship to the User Focus record.
Then those fields will be looked up down to ALL Parts and Parts which meet some complex criteria will be displayed immediately on the Descrepancy record. The user can then click a button on the part record to select it whatever that means - presumably it means to add a record on a table somewhere or to edit the Descrepancy record to to assign the cause of a problem to a Part. That same button could also redirect to the original list of 15,500 Discrepancies to be coded, however now the report will "only" be 15,499 records long and you just put a bunch of staff onto it all hammerin' away until you beat that list down to zero records.
So the goal is to minimize the clicks and make every one count since you are saying that a Human needs to have a quick look to interpret the comment and then assign the blame to a part.
It's probably just an hour or two of one on one consulting time required.
mark.shnier@gmail.com www.QuickBaseCoach.com
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
markshnier2@gmail.com
------------------------------
I do know how to do this.
My thought is that when a user views a Discrepancy, the form will take data from the Discrepancy Table (Discrepancy #, Machine #, and Discrepancy Date) and will display all Parts where Discrepancy Date falls between Part Installed Date and Part Removed Date, and Discrepancy Machine # equals Part Installed On Machine # . So the User will be given a list of all parts that were on that machine on that date, and they can choose the correct part.
I can help you one on one to implement a solution, but here would be the proposed workflow it this meets your need.
The user views a Discrepancy and on that record click a button. The button will edit or add to a table of users called User Focus table where the key field is the Userids. The particulars of the Descrepancy record will looked up by a reverse relationship to the User Focus record.
Then those fields will be looked up down to ALL Parts and Parts which meet some complex criteria will be displayed immediately on the Descrepancy record. The user can then click a button on the part record to select it whatever that means - presumably it means to add a record on a table somewhere or to edit the Descrepancy record to to assign the cause of a problem to a Part. That same button could also redirect to the original list of 15,500 Discrepancies to be coded, however now the report will "only" be 15,499 records long and you just put a bunch of staff onto it all hammerin' away until you beat that list down to zero records.
So the goal is to minimize the clicks and make every one count since you are saying that a Human needs to have a quick look to interpret the comment and then assign the blame to a part.
It's probably just an hour or two of one on one consulting time required.
mark.shnier@gmail.com www.QuickBaseCoach.com
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
markshnier2@gmail.com
------------------------------