Hi Doug,
You will need a Numbers Table with the 'pre assigned unique numbers', linked to the Members Table.
The Numbers Table will also need a Field to hold the number of tickets bought for that Number.
When the Member logs in and enters their unique number, it can be used to identify the Member and Location, then open the Form.
You will need a Query to check that the number of tickets sold for that location is less than 350. If the number is 349 then only a single ticket would be allowed. If the Member wants two tickets then give the option of 1 Ticket Only or WaitList.
The number of tickets left(or available) can be found using a query.
Is access to the DB by one person at a time or multiple users?
Hope that gives you ideas.
Regards, Clive.
--- In MS_Access_Professionals@yahoogroups.com, "D" <citypal@...> wrote:
>
> I am working on an event where I will have 700 tickets available for distribution and I am almost sure the event will be sold out. I need to divide the total number of tickets equally between two locations, each propective attendee will be permitted to order through an pre assigned unique number (no duplicates) and the maximum number of tickets that any one person can order is 2.
>
> How do I design the base, tables, queries and reports so that:
>
> when the total alloted tickets per location are exhausted the interested parties will be referred to a different table/form that will wait list them in order.
>
> I have some ideas about how this can be done, but I don't have weeks to try it out and I need to get this designed and up quickly.
>
>
> If there is any help out there I would appreciate it.
>
>
> thanks
>
> Doug
>
Tidak ada komentar:
Posting Komentar