dmcafee at pacbell.net
dmcafee at pacbell.net
Fri Apr 8 15:30:54 CDT 2005
This isn't a "one vehicle specific" or "work performed" database. It is more along the lines of your last paragraph. I work for a company that supplies the auto industry with those types of Dbs. The trouble is, that everything is always denormalized. The system I am now working on will be a supplement to the current CDs, since they're data is usually 6 months into the year before it is published. This may possibly be web based, but I am currently doing the rapid design as an ADP to get a working demo. I was thinking since I have a chance to get the design right, I might as well do that. David -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Dan Waters Sent: Friday, April 08, 2005 12:17 PM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] Vehicle maintenance database (cross posted) Hi Dave, This is just me but I would combine all these tables into one. Everything here defines the vehicle itself. Make a tblVehicle with appropriate columns. You might be able to use the VIN as a no-duplicate index value. A related table would contain information about each maintenance event - work done, cost, hours, owner (maintenance requestor), mechanic, etc. Or, you might make a table using customer information, and then the vehicle table would be subordinate to that. Each customer will have different vehicles. The shops where I take my car to get repaired seem to have fairly good maintenance databases. Perhaps buying one of those would be what you're looking for. HTH, Dan Waters -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of dmcafee at pacbell.net Sent: Friday, April 08, 2005 1:45 PM To: ACCESS-L at PEACH.EASE.LSOFT.COM Cc: AccessD at databaseadvisors.com Subject: [AccessD] Vehicle maintenance database (cross posted) I was given a task to quickly come up with a vehicle maintenance schedule database. before I get further, I was wondering if anyone already has something in place. If not, this is what I have so far: tblModels: ModelID PK Model (Camaro, Corvette) tblAutoMfg AutoMfgID PK AutoMfg (Chevrolet, Honda) tblMfgModels MfgModelID PK AutoMfgID FK ModelID FK tblYears YearID PK ModelYear (2005, 2004, 2003...) tblAutoYears AutoYearID PK YearID FK MfgModelID FK I'm looking at schedules that can be either light duty or heavy duty The maintenance schedules can also be either date based or mileage (or kilometer based). Something like Oil Changes, every 3000 miles or 3 months. But some items have only date based services and others have only mileage based service intervals. I was thinking something like tblMaintenanceTasks MaintTaskID MaintTask (Oil Change, Rotate Tires...) tblIntervals IntervalID Interval (3, 3000, 7500...) IntervalTypeID tblIntervalType IntervalType (Miles, Months) But I was also thinking of making tblIntervals, a little less normalized, something like: tblIntervals IntervalID IntervalMiles IntervalKilos IntervalMonths I have also not been told if we will be drilling down into sub model type (i.e. Mustang GT, Mustang LX), so for now, I am assuming that I will be relating these suggested service maintenance intervals to tblAutoYears. Any suggestions? TIA, David McAfee -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com