I've completed thru #3....

[Mmoney13]

Does this look right? Do I have 3c correct? When i create a new tbl for Billing Addresses how do I pull in fields from existing tbl??Always_inwork.zipFinalExam_Instructions.pdf

[June7]

Suggestions:

Don't use spaces or special characters/punctuation (underscore is exception) in field names. This follows the convention used in the original two tables. The actual field names do not have spaces, although the captions do.

ServiceID in tblService could be Autonumber.

Open the Relationships builder and establish appropriate joins and properties as described in the assignment.

You have repeated the service types in tblService. Each service should be a unique record (not considering the primary key for record uniqueness). For example, records 3 and 4 are duplicates and should be only one record. Same for 7 and 8, 9 and 10, 12 and 13. Will then have to correct the records in tblServiceCall. For example, records 9 and 10 should both have the same ServiceID number. Understanding reason for this is basic to understanding concepts of relational database and data normalization. Actually, correct this data before building the Relationships.

Billing address should not be the same as the service address and should not already be in tblCustomer. Only those clients that have a different address for billing should have records in tblBillingAddresses. The assignment shows 3 records for this table. This is a data entry task to create the 3 records.

[trevor40]

Why is it that everybody says don't use spaces in field names?

they seem to be a lot better to understand?
Just use [ ] to contain the field name anyware it's used,

me.[first name field for employee]
me.firstnamefieldforemployee
me.first_name_field_for_employee

[June7]

Because you have to remember to always type the [] in code and in query expressions. I am lazy and forgetful. I like the name as a single unbroken string, like variables in code.

And that's the convention the instructor for this assignment used.

[trevor40]

So it's a personal thing more so than anything else. I just think that it should be up to the individual.

actually after looking at the asignment it has a mixture of name types for fields and single part names for table and form names.

I'm allways checking for those [brackets] and in general I allways put them in.

Anyway for your assignment I will only give general advice, the rest is up to you.

Use the built in help from the access interface and also use the built in help from the VBA interface.

Microsoft provides help online for all functions operations of access without any bias towards any preferences prefered by some users. including mine!

Back to basics, table design first then onto the rest of the DB.
normalise the tables prior to creating any queries, forms or reports.
use debug and the imediate window for checking results and tests

[June7]

I did say it was a suggestion and yes it is personal choice. I also think less experienced developers will have fewer frustrations if they follow that guideline.

The two tables created by the instructor were tblCustomer and tblAccessPlan. None of the field names have spaces.