Greetings All,
I am currently using dummy houses to hold "Pre-Paid" tickets. A constituent pays for tickets in advance and then they "exchange" into performances once they go on sale. It is basically a subscription sales method. I want the exchange to happen in a new order where our reps book the new seats and then return the pre paid seats from the dummy house so the money essentially transfers to the correct performance. To do that, the tickets need to be printed, so I am trying to automate a "fake" printing process where tickets are automatically marked as printed in the dummy houses without actually having to run a batch print.
I have pulled the basic function from the TP_PRINT_TICKET procedure and I currently have:
UPDATE tx_perf_seat SET seat_status = 13, locked_by = NULL, prior_seat_status = 8 WHERE perf_no = @perf_no AND seat_status = 8
If I am correct, this would mark all of the "reserved, paid" seats in the designated performance as ticketed so they can be returned in a Ticketing order. My plan is to turn this into a utility that can be scheduled within the client so it can be added to our yearly season build procedure without relying on constant back-end work.
I know this is fairly simplistic, but it seems like this should work...but I would welcome input from the community. Can anyone foresee any unpredicted consequences here? Are there other tables I should be updating? Any comments are welcome.
Can you batch print to a Null printer? Or set the show up to mark as printed, a la simple museum admissions?
I don't want to have to patch print because I want to automate the process. The only way to mark as printed that I know of is to set up the mark as attended feature which I would rather not do since these aren't actually attended yet. I don't want to have to try and filter these performances out of all of the attendance reports.
Do you not filter those performances out already when you're looking at attendance since they are dummy performances?