![]() ![]() I wanted to see what that might look like on the back end of things - particularly table design and any calculated fields.īut Northwind doesn't seem to actually work. What I was hoping to explore - and is my only question - is how does Northwind handle receiving partial purchase orders - meaning a purchase order is submitted for purchase of one item, quantity = 10K but only 2000 can be shipped at a time. ![]() So I started trying to figure out the workflow of it - and was instantly stymied. I took a look at the Northwind sample db and - from the outside - it looks like it would fit the bill easily (although I would nix the PO submittal and approval part of it. Our purchasing department struggles mightily with our ERP primarily because the ERP was outsourced and we have no control over form or query design - and are not nearly big enough to swallow the cost of DB ongoing development - especially when our industry is a niche market at best. This opens a broad horizon in front of me. Change the definition of Customer_Table toĭbTable(Customer_Number, Customer_Field) = Re-evaluate Customer_Table.Without going into a long drawn out story - the powers that be at work love what I am doing with my QC db.so much so that I've been tasked to develop another one that initially was to record inspections of hardware: incoming, purchased on a PO and later shipped out with a job.Index tmp := DbLabels(Customer_Number) do subset(tmp "CustomerID") Change the definition of Customer_Field to:.Create a new index node, name it CustomerID, defined as:ĬopyIndex(DbTable(Customer_Number,"CustomerID")).The data is now imported (as shown below).įor convenience, we may want to use the CustomerID column of the table as the row index. ![]() Drag a variable node to the diagram, name it Customer Table, and define it as:.Drag another index node to the diagram, name it Customer Field, define it as:. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |