And if you continue with this level of selfmotivation you aren't going to finish the year.

If you ask a specific question the people here will gladly reply. And you will get the benefit of years...

Have a look through this http://www.geekgirls.com/databases_from_scratch_1.htm

Very good intro to DB design.

Your hair's a mess and your shoes don't go with your trousers. And when DID you think that that tie went with that shirt! :)

Simple pragmatic rule.

1) He's the boss.

2) If he's wrong refer to rule 1.

1) First normal form removes repeating items. http://en.wikipedia.org/wiki/First_normal_form Here the repeating items can be OwnerContact (an owner may have a number of different contact details),...

Sorry Ramy but you have some way to go before you become a fully skilled DBA. From reading your posts you have learned the fundamentals very well. You now need to get into a company position with an...

1) First Normal Form - http://en.wikipedia.org/wiki/First_normal_form
To get to FNF we have to remove the repeating fields. Current Country,Current Region,Current Site,Current Locale Start...

No Ramy, just my comments on the DB design in this thread.

I have a number of points here.
1) If each row in the EMPLOYEE_WORK table has a ROWID IDENTITY column (or similar) then you don't need the date column. INT columns are smaller that DATETIMES as...

Now that is quite a good question.

Does the data about the stock belong (totally) to the book itself? Or is the concept of STOCK a seperate item?

The data could go in a number of places, but...

Normalization is actually fairly simple. To convert data from one form to another you apply a single, simple, rule to that data. To move to the next level of normalization apply the next rule etc....

You include ROOM_PRICE in the ROOMS table and the ROOM_TYPE table. It should only appear in one of these.

The choice is yours. ROOM gives precise control over room pricing, ROOM_TYPE gives easier...

Originally I thought that this was in the wrong forum. But I was wrong.

Your query regarding the foreign key violations should be fairly trivial if you trace back through all of the tables...

To answer a quick question, I cannot understand why you think that you need to de-normalise the data.

An ERD is (or should be) created BEFORE the database. The DB definitions are based upon the...

Let me get this straight.

You're a TECHNOPHOBE doing a DEGREE course with a large COMPUTING involvement and you want US (who are TECHNOPHILES and [mostly] have finished our degrees) to do this...

This type of question can most easily be answered by normalising the data.

Correct nomalisation will show which of these entities 'owns' the others. For instance Can a CASE have more than one...

I agree with Ramy.

The way your question is worded the only answer we can give is MAYBE. :)

I have used this style of table reuse before and always handled the releationships in the application.

As you say if you try to set foreign key relationships from either the COMPANY or CONTACT...

I don't think that you've actually asked the right question. The answer to the question that you have asked is "What ever you want to."

This is going to be very difficult to do as you do not give any user requirements.

MS Access has sample templates which, I believe, provide an attendance monitoring DB and a material (asset?)...