Ramesh (1/14/2009)
Jeff Moden (1/14/2009)
Ramesh (1/14/2009)
Jeff Moden (1/14/2009)
Never mind... not enough coffee... I see it. And, I agree with Seth... unless you have some additional information, this is definitely not the way I'd output from an inventory system.Aaaah...;), That's what I've done in our payroll system....:):)
Heh... payroll, inventory... doesn't matter. I don't understand the business rules for matching two seemingly unrelated rows.
I guess it just like showing data in columnar manner, that you see in payslips. And also there are some not so good reporting tools (which i use) that doesn't do what it should be doing...
Ah! Ok... I get it... the data being presented is for a single "employee" (or whatever), all the rows in the example are for a single employee, and you don't really give a hoot what the order is so long as all the deductions (for example) are on one side. Heh... that also means, this is RBAR on steriods because you don't have a decent reporting tool to do it for you and no one wants to (or can't) write an app to do it for you.
How is the current solution working so far a performance goes? I ask because I can just see someone thinking they need a While loop to loop through each "employee" (or whatever) and that's patently not the case.
--Jeff Moden
Change is inevitable... Change for the better is not.