I agree on Carl but you can also put everything in one table for easy query
purpose but you will have two subforms, one is for the Food Details and one
is for Wine Details. The 2 subform should be the same size and in same
location and you can do the trick of visible=yes/no. What I mean,
If ProductType="Wine" then
me.WineDetails_subform.visible=True
me.FoodDetails_subform.visible=False
else
me.WineDetails_subform.visible=false
me.FoodDetails_subform.visible=true
end if
-----Original Message-----
From: [email protected]
[mailto:[EMAIL PROTECTED] Behalf Of Pete Harrison
Sent: Monday, October 24, 2005 5:14 PM
To: [email protected]
Subject: [AccessDevelopers] Database design considerations
I am creating a new database for my brother who runs a food and wine
shop.
It's going to be used for basic stock control and a in-shop 'kiosk'
type application showing a customer details about the product, an
image etc.
Looking at the table design for the products table, many of the fields
for food or wine are the same (barcode, suppliers ref, product ref,
name etc), but then when it comes to the 'information', things go
wildly different, e.g. wine might have vintage, maker, vinyard,
whereas food wouldn't use these fields.
It it best to have a products table for the common fields and
wine_details and a food_details tables for the particular details?
Regards
Pete
Please zip all files prior to uploading to Files section.
Yahoo! Groups Links
------------------------ Yahoo! Groups Sponsor --------------------~-->
Get Bzzzy! (real tools to help you find a job). Welcome to the Sweet Life.
http://us.click.yahoo.com/A77XvD/vlQLAA/TtwFAA/q7folB/TM
--------------------------------------------------------------------~->
Please zip all files prior to uploading to Files section.
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/AccessDevelopers/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
