If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
database design
A manufacture table stores make, model, price, colour and options information.
The available make calibras has two models 2.0i and 2.0i16v and bmw car two models p610 and p612. My question how to create a database that doesn't allow the user to enter the make of the car as bmw and model as 2.0i. |
#2
|
|||
|
|||
database design
You can use the validation property of the field in the table.
-- KARL DEWEY Build a little - Test a little "Astitva" wrote: A manufacture table stores make, model, price, colour and options information. The available make calibras has two models 2.0i and 2.0i16v and bmw car two models p610 and p612. My question how to create a database that doesn't allow the user to enter the make of the car as bmw and model as 2.0i. |
#3
|
|||
|
|||
database design
On Tue, 13 Nov 2007 14:37:03 -0800, Astitva
wrote: A manufacture table stores make, model, price, colour and options information. The available make calibras has two models 2.0i and 2.0i16v and bmw car two models p610 and p612. My question how to create a database that doesn't allow the user to enter the make of the car as bmw and model as 2.0i. Typically one would have two tables in a one to many relationship: Makes related one to many to Models. The Models table would have a Make field as a foreign key, referential integrity enforced, to the Makes table. Only authorized users would be allowed to add records to the Models table (and you'll have to have some trusted user, maybe yourself). John W. Vinson [MVP] |
Thread Tools | |
Display Modes | |
|
|