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
Sheela Sur-Luk said:My thought is to set up a nightly SQL Server job that just does
I assume you mean an "early morning SQL Server job"...
I don't know off the top of my head, but I'd check to make sure that NSCAN is looking at T_PERF, and not looking at the ticket itself (i.e. TX_PERF_SEAT or similar location).
Yes! It will run after midnight.
Thanks, Gawain! My main concern is there are other places I need to update the perf_dt that I'm not thinking of.