Relationship problems - IDEAS NEEDED!!

[Mikebyrne]

I've completed the Relationships on my online store project database and put the tables into a word doc so everyone can view

Does everyone think they look ok? If not, all opinions are welcome!

I've also 2 questions:

1) Should I create a seperate table for Usernames & Passwords?

2) Should I make the CD, DVD & Games table in a single table?

 

[Guus2005]

I WOULDN'T USE SPACES OR SLASHES IN MY FIELDNAMES

1 - NOT NECESSARY
2 - FINE THE WAY THEY ARE. SINCE THE TYPE OF INFORMATION IS SLIGHTLY DIFFERENT.

TABLE ORDER DETAILS PK IS WRONG. USE ORDERDETAILSID WITH ORDERID AS A FK. THE RELATION BETWEEN ORDERS AND ORDERDETAILS SHOULD BE 1-N.

USER AND CLIENT ARE THE SAME? IF NOT, INTRODUCE CLIENTID INSTEAD OF USERID.
A USER IS SOMEONE THAT USES YOUR APPLICATION.

OFCOURSE YOU MAY IGNORE ANYTHING I WRITE.

HTH

P.S.
Next time don’t use uppercase characters.

 

[Mikebyrne]

Thanks for the advice! (Fixing up as I type)

In relation to the userid and passwords I was told it would be a good idea to keep the passwords in a seperate table.

How would I set that up so I could keep a relationship with the Users table?

 

[Guus2005]

You could put it in a separate table but you don't have to.

Create a table called passwords with userid and password fields. Make sure the inputmask of the password field is "password".

Enjoy!

 

[Mikebyrne]

So just create a relationship (1:N) between the userid of the password table and userid of the Users table?

 

[neileg]

You would have a 1:1 relationship, that's why Guus2005 said it's not neccesary. Usually you would only implement a 1:1 relationship if you wanted to use Access security to protect the passwords but allow users to see the user table.