Search results

You've raised some good points Simon. Thanks for all your help

My main concern with going the one table route was having blank fields but that seems to be ok Does my order system look ok to you? ie Users being able to order multiple iems on one order etc

How would you suggest I merge the temp into the users table??

Thanks for the input, I'm agree with you about the 3 tables but think the guy over my project wants it in 1 table. (dont know why!!!!) I prefer 3 tables. Do you think having the password on a seprate table is right?

Hi, I'm doing a database for a CD, DVD, Game website could you take a second to review it and give me suggestions to improve things. I've included my old and revised database to see what if done

Hi, I'm doing a database for a CD, DVD, Game website could you take a second to review it and give me suggestions to improve things. I've included my old and revised database to see what if done

Ok, I've done a revised DB with the merged tables. Take a look and give me your opinion

I'll put a copy of the DB up too for anyone that wants a look The only problem id have with merging the tables is the empty fields, it probably isnt good practise leaving fields blank but on the other hand it isnt good practise having similar fields on tables

Thats what I originaly thought but someone suggested otherwise so I'll have to test it out. Other Issues: 1) Should I merge the 3 product tables (CD, GAME, DVD) into one table?? 2) Is having the password table seperate a better way of doing it as opposed to having the user details and...

The Temp user table is a holding area so that when a user confirms via an email link their detials will be passed into the users table The one problem I can see is that I'm not sure if users can buy more than one item on a single vist with my current layout Any suggestions?

Could someone offer suggestions on how to improve the database or the general structure of it? All suggestions are welcome! (Its an online retail project selling DVD's, CD's & Games)

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

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?

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...

I'm currently doing a project that has a web based front end to a database. I've decided to do a online retail store ie www.cdwow.ie At the moment I've 4 tables (Games, DVD, CD, Users) but im not sure what relationships to set between them. My second issue is how to record user orders...