RE: [AccessDevelopers] Database design considerations

[Carl Beck]

I would recommend using different tables for each to make things easier on both development as well as user access. These POP systems usually have many different tables the access and creating more tables makes data access faster if you are going to implement multiple front end locations(eg: store owner, kiosk for customer, sales team). Carl   From: AccessDevelopers@yahoogroups.com [mailto:AccessDevelopers@yahoogroups.com] On Behalf Of Pete Harrison Sent: Monday, October 24, 2005 9:14 AM To: AccessDevelopers@yahoogroups.com 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  Visit your group "AccessDevelopers" on the web.    To unsubscribe from this group, send an email to:  [EMAIL PROTECTED]    Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.