Wrox Programmer Forums
Go Back   Wrox Programmer Forums > Visual Basic > VB 6 Visual Basic 6 > VB Databases Basics
|
VB Databases Basics Beginning-level VB coding questions specific to using VB with databases. Issues not specific to database use will be redirected to other forums.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the VB Databases Basics section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old June 2nd, 2004, 09:21 AM
Registered User
 
Join Date: Jun 2004
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default Looking for design direction on database

I'm working on a database and hope someone could help me with a direction to head. I don't have all of the details worked out yet but the database is exactly like an autoparts selection database. I'm using VB.NET and SQL.

Here's what I want to do:
Make: Model: Engine: Part:
 Chevy
      Corvette
              425
                       Headlight
              350
                       Headlight
      Camaro
      S-10
 Ford
 Dodge

Looking at my example there are selections based on a previous answer and if you were to select Ford for example you wouldn't see Camaro, etc but you would get the Ford cars. I need to ultimately drill to a SKU type number for the last items in the "Trail". Every car has a headlight but Mustang headlights are different from Corvette.

Does anyone have a clue to this? I'm looking for how to structure the tables. I think I can figure out the VB selection tree once I get the tables setup. I also want to maintain 3rd normal as much as possible. I know it has to be a common thing.

Thanks,
Phil

 
Old June 29th, 2004, 02:26 AM
Friend of Wrox
 
Join Date: May 2004
Posts: 105
Thanks: 0
Thanked 0 Times in 0 Posts
Default

It`s really a very common thing!!!

Try using multiple keys on your tables...

(e.g. Brand:Corvette Model:425 is a unique key... different from Corvette 300. )

So when you`ll search for e.g.

SELECT * FROM table1 WHERE BRAND=FORD
you`ll not get as a result the Camaru model!

I hope that I can understand your problem... If so I think that you `ll find the solution very easy! :)





Similar Threads
Thread Thread Starter Forum Replies Last Post
Database Design cf2006 BOOK: Beginning Visual Basic 2005 Databases ISBN: 978-0-7645-8894-5 4 August 2nd, 2006 03:50 PM
Database design tsimsha Classic ASP Databases 0 February 3rd, 2006 03:28 AM
Database Design Help malhyp BOOK: Access 2003 VBA Programmer's Reference 1 November 3rd, 2005 06:33 PM
Database design, please help! mumick SQL Server 2000 0 January 13th, 2005 02:57 PM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.