If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Designing a database for selling suites at Sports stadium
Hello all...!!!
I am in the process of designing a database for a company that sells suites (i.e. grouping of ten seats) at a Sports stadium. I have so far created the following tables: Customers - general customer details. Suites - this has field for Name of Suite and Sold (yes/no); My issue is the following: 1) A particular suite (lets say number 1001) can have 2 different prices. For example $2,500 if sold by itself, or $2,000 if sold with other items; 2) When doing data entry to record the sale of a suite the user would only like to see those suites that are left to sell; Any thoughts on: 1) What additional tables I might need to record the sales transactions and also account for the different pricings; 2) How would I setup the data entry form to only show those suites that are still available for sale? Any help would be greatly appreciated. Regards James |
#2
|
|||
|
|||
Designing a database for selling suites at Sports stadium
1 Vous avez besoin de table de "sales transactions." Si vous deciderait des
prix durs, puis une autre table est necessaire pour une bonne forme. 2 La feuille d'interface aie une graphique qui les presente. Comme "drill-down" |
#3
|
|||
|
|||
Designing a database for selling suites at Sports stadium
Since this is a tables/db design database, I would make these suggestions
regarding your table structu I would not use a yes/no field in the Suites table for Sold. Consider creating a "Sales" table with fields like: tblSuiteSales ============= susSuSID autonumber primary key CustomerID SuiteID SaleDate SaleAmount StartDate EndDate SaleComments The trick to finding the suites that are available is to create a query of suites that are not available. Then join this to the table of all suites with a join that includes all records from the suite table. Set a criteria under the SuiteID of the "sold" query to Is Null. -- Duane Hookom MS Access MVP -- "James T" wrote in message ... Hello all...!!! I am in the process of designing a database for a company that sells suites (i.e. grouping of ten seats) at a Sports stadium. I have so far created the following tables: Customers - general customer details. Suites - this has field for Name of Suite and Sold (yes/no); My issue is the following: 1) A particular suite (lets say number 1001) can have 2 different prices. For example $2,500 if sold by itself, or $2,000 if sold with other items; 2) When doing data entry to record the sale of a suite the user would only like to see those suites that are left to sell; Any thoughts on: 1) What additional tables I might need to record the sales transactions and also account for the different pricings; 2) How would I setup the data entry form to only show those suites that are still available for sale? Any help would be greatly appreciated. Regards James |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Help! Database mysteriously deleting | Mark | General Discussion | 10 | October 20th, 2009 04:03 PM |
Toolbars, Drop-Down Menus | Rick | New Users | 1 | September 21st, 2005 11:17 AM |
HELP! CANNOT CONNECT TO SQL SERVER | Glint | General Discussion | 19 | May 9th, 2005 02:47 PM |
Designing donor database | AnnT | Database Design | 1 | April 15th, 2005 06:56 PM |
Database periodically needs rebuild and locks users out | spectrum | General Discussion | 2 | July 13th, 2004 06:24 PM |