develop a logical database design in Access that contains a minimum of 5 tables. Using the Database Relationship View, all tables must be interconnected by the appropriate 1 to many relationships. Standalone tables or tables with 1 to 1 relationships should not be incorporated into your design (please check with your professor if you feel that an exception is valid). Tables in your database must be given understandable names and descriptions. Variables (or columns) in the tables must be defined across a range of data types including; text, date, number. You must use a MINIMUM of 4 different field data types in your design. Each table must have a primary key (or composite primary key) defined. All tables must be related with the minimal amount of relationships. Typically that would mean you should end up with one less relationship for the number of tables in your solution (i.e., a 5 table database only requires 4 relationships in order to be fully integrated, any additional relationships would be considered redundant and would need to be justified in your design approach)

evolve your database design into a working database that will demonstrate the following skill components that have been introduced in the Access portion of the course including: - At least 10 data records in each of the tables (there may be exceptions, but use this as a guideline) - Establish reasonable and correct relationship among ALL tables in the database. Please note, that all tables must have relationships to at least other table in the database. - At least 3 different types of summary or detailed queries (i.e. Basic, multi-table, with calculated and derived values, summary, filter, sort, etc.) based on the data provided in the tables. - At least 1 type of data action query (that can create, and update or modify or remove data in your tables) - At least 2 forms to facilitate data entry. Forms must be show contrasting form design approaches and should be appropriately designed and labelled for an end user (not a database administrator) In other words, field labels should avoid database language and be clearly labelled and laid out on the form in an intuitive way (i.e. do not provide forms based on your table layouts. Forms must avoid single table sources, and should integrate information across tables for ease of use for the end user. - At least 3 reports to display your data in an attractive and professional manner. Reports should show a variety of techniques, and demonstrate different layout formats, and be contrasting from each other in both function and style. - Some demonstration of automated data management in the form of action queries (Update or Delete) and/or Macros (either stand alone, or embedded) is required - Demonstrated capability to export data out of Access and into Excel for further decision support analysis (Tip: Develop queries to extract data into a tabular format. During the Excel development phase of the project, you will be making a data connection to these Access query results in order to drive data into your spreadsheet for further analysis. For this phase the important thing is to have predeveloped queries that can be used to extract and transform your data so that it can be loaded into your spreadsheet as input data source) - Optional: You may also use Excel as an input data source and create a data connection to your Access Database, however, it is more common to have an Excel spreadsheet connected to a database (i.e. the data import connection is established from within Excel such that the database information is "pulled" into the spreadsheet for analysis), rather than having a database connected to an Excel spreadsheet (i.e. the data export connection is established from within the Access Database such that the database information is "pushed" into the spreadsheet for analysis)