Here are the statements that need to be conducted below, but I am having trouble attaching the database file. How do I link the .dbs file here?
There's the link to download the .dbs file. I am needing it by Sunday if that is ok with you?
Thanks again for the assistance. I really appreciate it. One question I have is that how did you construct the queries in Access at all? This might be some simple question I'm asking, but this is where I'm getting confused at the moment. lol
Attachments are only available to registered users.
Yea, I think that's my biggest problem there. I get confused on what to do once I go through the Query Design Wizard. I have no idea how you were able to obtain the queries that I listed for you. Do I have to "run" anything from the answers you provided me earlier though? Or are all the Queries already there? Sorry for the extra questions Eljon, I just want to somewhat get a brief understanding on how you did this :p
I was wondering if you could help me with Microsoft Visio? Please let me know if you would be able to assist me. Thanks
I had a couple questions regarding constraints and database redesign.
First Question: Business requirements are enforced by implementing database constraints on tables and columns. The database constraints available include the following.
Give a business requirement and the constraint that could be implemented to enforce it. Explain the constraint you choose, and give the SQL to implement the constraint in the database.
What are the long-term problems when these constraints are not implemented?
Second Question: After your database was put into production, a design flaw was discovered! One of the relationships modeled as a 1:N relationship was really an N:M relationship. The database issue invoves the following tables, with PK italicized and underlined.
VEHICAL (VIN, Make, Model, Color, LicenceTag)DRIVERS (DriverLicenseNo, LastName, FirstName, Address, Zip, VIN)ZIPCODE (Zipcode, City, State)
Which 1:N relationship should be an N:M relationship? How would you redesign the database to correct the issue? What else must you consider when updating the structure of your database tables?