A Microsoft Office (Excel, Word) forum. OfficeFrustration

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.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Database Design
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

database design



 
 
Thread Tools Display Modes
  #1  
Old November 13th, 2007, 10:37 PM posted to microsoft.public.access.tablesdbdesign
Astitva
external usenet poster
 
Posts: 2
Default 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  
Old November 13th, 2007, 11:55 PM posted to microsoft.public.access.tablesdbdesign
KARL DEWEY
external usenet poster
 
Posts: 10,767
Default 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  
Old November 14th, 2007, 01:36 AM posted to microsoft.public.access.tablesdbdesign
John W. Vinson
external usenet poster
 
Posts: 18,261
Default 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

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 11:50 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.