I think that whether you use one table or three the processing overhead will be the same - you will still need several seeks which will take the same amount of time whether they are on one table or three. A single table will give you more flexibility and will be easier if the user wants to enter a code directly.
Can't help on the Gui I'm afraid. John Weller 01380 723235 07976 393631 >Hi guys- > > I'm curious what prevailing opinions you have about setting up repair > codes with multiple levels for the database. The repair codes I'm > specifically tasked to deal with currently have 3 levels such as: > > 5110 - Brakes > - 01 Front > 00 - Pad Change > 01 - Pad Change Cut Rotors > - 02 Rear > > 5120 - Towing > - 01 Accident > > > I was thinking of doing it in 1 table where sub codes link back to > the parent. Are there other, better ways to do this? This allows some > flexibility I belive, such as adding new levels if needed, but it > also might be kind of slow to parse a given code. > > > _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
