This Ticket Manager system had its beginning in the early 1990s

The first events were at the Bloomfield United Methodist Church in Bloomfield, 
Connecticut:

Beef Dinners 1990 - 1994           Served: 113 - 142 meals
Chicken Supper 1991                Served: 159 meals
Harvest Suppers 1993 - 1994        Served: 206 - 343 meals
Strawberry Festivals 1992 - 1995   Served: 145 - 179 meals/deserts
High Tea Celebration  1995

  and more recently at the Niwot United Methodist Church in Gunbarrel, Colorado:

Soup, Soup and More  1995 - ...    Served: 115 - 147 meals

Numbered tickets have been a feature from the start in 1990.
  Why numbered?    
  1) When the tickets are numbered, it is possible to track which volunteer 
ticket seller they were issued to and if the ticket was ultimately used.
  2) It also makes it possible to 'deassign' a ticket when turned back in by the 
ticket seller.
  3) It is much easier to convince volunteer ticket sellers to take some tickets,
 and attempt to sell them, when they know they can simply turn them back in, if 
not sold.
  4) The entire process can be kept 'transparent' and 'traceable' with the help 
of the available reports.
  5) Interested persons can have confidence in the ticket selling process.

The earliest record keeping was handled in Lotus 1-2-3 spreadsheets until, in 
the mid 1990s, I moved the record keeping over to Access databases, the TktMgr 
database for Forms and Reports and separate databases for the data from each 
event.

Recently I have built a TktMgr Visual Basic program that is easier to deploy to 
non-profit organizations.

The TktMgr system has had the ability to view and print reports via MS Access.  
They, now, can be viewed and printed via web browsers.

I have recently incorporated the functionality to design and print the tickets 
from within Ticket Manager (TktMgr) application.

I have been asked if the ticket numbering can be modified to represent theater 
seats.  I have not thought of a way, but who knows?