Hi All,
I'm playing around with access areas on NScan before we begin using them. I have set things up in the TR NSCAN ACCESS AREAS table and TR NSCAN PROFILES. One thing I'm finding is that I consistently get entry denied if I don't have enough info in the TR NSCAN ACCESS AREAS table.
For example, if I just have area code, desc, perf str, start dt, end dt, max entries and prompt qty, I get entry denied on the scanner each time despite the ticket being for the correct perf and my dates corresponding to both the perf time and my scanning time. However, if I add in a price type ID, it works as I'd expect.
The scenario we want to have is to have tickets for a performance scan into a pre-performance event. So I would think that all I'd need in the system table is the perf ID but it isn't seeming to work. Since all perf tickets are valid, I don't want to add all price types to the access areas system table because that feels like overkill.
Thoughts? How much do you fill out in your Access Areas system table?
Thanks in advance!
Jenny
Jenny,
We're going to begin scanning special access areas next season and I have a question that you might be able to answer. Do you have dedicated scanners for these access areas or are you using the same scanners set to scan both a facility and an access area in LTR_NSCAN_PROFILES? Essentially having your current scanners do double duty?
Michele
Yes, the scanners will have the ability to double duty but we are going to have dedicated scanners for the access areas when we have special events that require the scan. I think it would be tedious for the person scanning to have to change to ticket events from special access areas so we wanted to avoid that.
Our plan on a show date (note, we'll have our first event on Sunday so this is the *plan* and we'll see if it works!):
1. FOH will program the system tables for the access areas (leaving all other settings for ticketed event scans just adding what is needed for access areas on the device). So adding perf string (and anything else needed to approve scans) in TR NSCAN ACCESS AREAS and access area in TR NSCAN PROFILES.
2. Front of house staff checks out the programmed scanners for the special events staff to use at the access areas.
3. End of the night, FOH removes the access area details in system tables for use on ticketed events at a future performance.
So just a few minor adjustments to the scanner settings because we don't want to dedicate scanners to a given purpose. We are trying to use all scanners as equally as possible so they all get the same wear and tear. In regular use, our TR NSCAN PROFILES table has a facility string that includes all of our facilities, we don't add perf strings for each performance.
Hope this helps, feel free to contact me offline if you have more questions!