Occasionally, a fat finger error will cause our software to generate 2 shipment requests for 1 order.<br><br>Therefore I am trying to create a report that will identify ONLY the orders with multiple shipments.<br><br>How best should I set up the report (selection criteria, parameters) to identify only these orders w/ more than one shipment attached to them?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Selection criteria: Multiple orders
- Thread starter bersh
- Start date
- Thread starter
- #3
Probably best to do it on the SQL side, cause most of your orders will not meet that criteria, and there is no point in overloading the network with useless traffic.<br>Normally I would use a stored proc to do this, but Oracle stored procs are not as easy to implement.<br>So, you could create a view or temp table, with the order number, and count of shipping requests. <br>In yer HAVING clause,<br>Count(shipping requests) > 1<br>If you applied other parameters (date range, etc) in the record selection formula, they will often be passed to the server.<br> <p>Malcolm Wynden<br><a href=mailto:wynden@island.dot.net>wynden@island.dot.net</a><br><a href= > </a><br>
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question