To Db or Not To Db

[Furgan]

I am wanting to create a quick reference guide for people to find a part number for fast moving parts utilizing dropdown menus.  The first menu item will be by "model number". Most models (approximately 300 in all) will have one part number associated with each item (such as air filter, coil, gasket, etc.). There will be around 5% of these that may have 2 or 3 different part numbers that would be separated by a range of "type" numbers. An example would be model 60100, type #'s 0100 through 0650 would use one series of part numbers, then model 60100, tpe #0651 and above would use another series of part numbers.

 

With that in mind, the first dropdown menu would list all of the model numbers available. Upon choosing model 60100 the second dropdown list would show "Types 0100 through 0650" and "Types 0651 And Above". When choosing either item a list of part names and part numbers would populate in a table.

 

My series of questions: 1) Would this best be handled using a database or an array? 2) If a database, would a single table suffice or be better using multiple tables? 3) If an array would be best could someone point me to where I can learn about arrays and interfacing with them?

 

My database experience is mostly using MS Access and have toyed a little with Visual Basic.

 

Thanks in advance for the help.

[Gath]

I'm kind of sleepy, so dont take my words as completly correct... it might not be

 

But, yes, a DB instead of an array.

 

And the DB, i' not sure i understood correctly the amount/relation of data, so i'll just trow some example:

 

id(model number?), name, type, associated_1, associated_2, some_other_data

 

So, 1 table should do it, as 300 isnt that mutch.

[HuggieBear]

1 table should do it, as 300 isnt that much

 

I'd say it isn't, one of my transactional tables is getting over 1 million rows a day, but then I'm using Oracle, so it can cope with it! 

 

Regards

Huggie

[Sorthy359]

a database would be much easier. you can use multiple tables for each kind of part and store different models in them. then you can make a page to add,edit,or delete parts. its more professional and wastes less time. even if i didnt have access or knowledge of databases,i would still use a flat file db.but i dont recommend that.i would use mysql.the commands are very simple and its a great db.