Union Query

I realize you might not be able to answer this if you didn't develop the db, or if you inherited it. I'm curious why you have a different order system for service and sales. What is in the service order that couldn't be handled as a regular sales order? In all the systems I've worked in, some service is just another "item" being sold.

Hi Thomas,
In my program, service came first, and the service order form links all services to a piece of equipment, which has many additional links along with mandatory entries.  In addition, I track labor as an entity of the Service Order and not another line item in the detail sub form. While it would be possible to combine into a single form, this just seemed more logical to me.  I did consider it, but ultimately thought this would be less work than having to deal with all the relationships and code that would need to be modified to accept an order without a customer's piece of equipment, labor, contracts and several other linked tables.  The suggestion of the Union Query worked perfectly, Thanks for that, Kevin

@ Jerry A. Thanks for your answer. I guess the service order coming first sort of muddied the waters. I've usually seen a work order document/system handle the preliminary data gathering process for service. And then the work order is added to the sales order as an optional field. It would be a process flow, kind of like a bid request>bid response>purchase order>shipping confirmation>warehouse receipt>invoice>voucher>payment for purchasing and accounts payable.