Why would you want two work order records with the same work order number?
I can see duplicating the customer info on a new work order or even duplicating all the information from the current work order onto a new work order, but why keep the work order number the same and thus produce two completely duplicate records?
Well I work in a machine shop that services parts. We have alot of things coming and going everyday. So I am trying to come up with something that will help organize this madness lol. I have that part in the header and in the body it displays 1 record. Each record needs to have a work order number that corresponds to a po given by a customer. The customer might give us 1 po with 5 items that need repair. So we put the same work order number to reference that po number. Also I am working on a delivery ticket system so that when you type in the work order number it will pull in all the info from that work order; customer name, po, job no, rig, and well info as well as the items listed.
I could give each item a different WO# but how would I get all the items to show up on the delivery ticket related to that same job.
We dont always get a po right off the bat if it is a rush job. Which is why I reference a WO#.
I am open to anything that you think would help.
I would be inclined to track by PO number instead of Work Order number, but it all depends in you your organise your data.
You could have just one Work Order for every PO and use a related table of WorkOrderItems to list each part that needs to be machined on that work order