I am looking for suggestions. We are doing some experimenting with future subscription orders that requires the orders to be paid, and I am sure I will have to do this entire operation several times. What is the cleanest way to handle mass payment of multiple orders in Test?
Clarke
At the Science Museum, we have automated attendance scans to produce an order. I'm sure you could add to it making it a batch insert of sorts. Let me know if you would like more info
I would like to see that!
cweigle@floridastudiotheatre.org
Thanks for that, Troy. It looks like, in terms of payment, it just marks due_amt & paid_amt as both being 0 in the appropriate tables (as well as setting appeal_no & source_no to be reasonable values in T_ORDER).