We are trying out a new way of booking drink vouchers in Tess as tickets to a large GA drink ticket "performance", where tickets can be scanned using Nscan and are valid/can be scanned for the entire fiscal year.
At first I thought we could just set up one performance with the performance date being the last day of the fiscal year. However, Nscan will only scan tickets that have a performance date during the day that it's scanning - we don't want to enter the drink ticket perf_no in the Perf_str column of TR_NSCAN_PROFILES as this makes the scanner only use-able for that performance.
My thought is to set up a nightly SQL Server job that just does:
UPDATE T_PERF SET perf_dt = GETDATE() WHERE perf_no = [drink ticket performance]
Are there any negative ramifications to updating T_PERF like this that I'm not thinking of?
Thanks!Sheela
I'm won't pretend to be enough of a SQL expert to comment on T_PERF updates, but will mention that we have set up drink vouchers as a fiscal-year-end perf for several years, and circumvented the scanning issue through our lobby flow. Drink vouchers are printed on standard ticket stock and then mailed or held at will call as appropriate, but don't get scanned at the door - instead, our concessions staff collects any physical vouchers used at the bar that night and delivers them to the box office, who then mark them as 'attended' via Record Attendance in the client as part of standard opening/closing. It's not immediate, but all the vouchers get marked as 'used' within a business day so we can confirm there's no funny business when someone claims they "lost" their drink voucher and asks for a reprint (which has happened!). Not sure if your lobby setup would allow for this but it's worked pretty smoothly for us!