Ticket Design Mask Question

Hi Daniel,

Did you ever find a solution for this?

Cheers
Sarah 

Hi Sarah,

Unfortunately, I was not able to come up with a resolution for this but realized afterwords that our legacy system did the same thing so it really wasn't a giant issue for us. If you hear of something though please let me know.

Thanks,
Daniel Williams

Box Office Manager
Flat Rock Playhouse
2661 Greenville Hwy
Flat Rock, NC 28731
Phone: (828)693-3893

I don't have the capability to test this right now, but I'm fairly certain you should be able to do this with some clever expression logic.

These ticket element masks are actually InfoMaker expressions, and having a full function reference is essential to understanding the full potential of what you can do with them. I've excerpted this reference from the full InfoMaker manual and made it available on my profile here:

InfoMaker Expression Reference.pdf

What occurs to me as a possible way to uppercase only the day part of the long date format would be to either compose the long date format yourself using the datetime functions (just uppercasing the ones you want), or by using Pos() and Left() to pull out and uppercase the substring that occurs before the first comma (the Day).

Thanks Nick.  My infomaker skills are sadly fairly limited and this document is great.  I still haven't been able to work out an infomaker expression that works to format the date with capital letters, but your message gave me the idea to instead create a user-defined element in LP_TICKET_ELEMENTS that would do the same thing.

If @ude_no = 1 and @customer_no > 0
and @design_type = 'T'

BEGIN

Select
@ude_value = UPPER(DATENAME(dw,perf_dt)) + ' ' + DATENAME(d,perf_dt) + '-' + UPPER(DATENAME(m,perf_dt)) +'-' +DATENAME(yyyy,perf_dt)
FROM T_PERF p
JOIN T_SUB_LINEITEM sl on p.perf_no = sl.perf_no
where sli_no = @cur_sli_no

END

Cool, Sarah! Though perhaps you might want to remove the 'and @customer_no > 0' — that will cause a failure if you print an anonymous ticket, no?

Ah yes, good point.  Although we don't allow any tickets to be sold without a consitutent id so in our case it won't be a problem.  Interesting that it's included in the sample code within LP_TICKET_ELEMENTS.

Ah yes, good point.  Although we don't allow any tickets to be sold without a consitutent id so in our case it won't be a problem.  Interesting that it's included in the sample code within LP_TICKET_ELEMENTS.