Hi Jerry,
The database may be fairly simple. For a start, one table would be enough.
Table: CarMaintenance
FIELDS:
MaintenanceDate (primary key)
Mileage
Garage
Cost
PeriodicMaintenanceType
Trouble description (memo field)
Work description (memo field)
But you could make it a lot more complex.
For example, you could create tables describing the various periodic
maintenance types:
TABLE:
PeriodicMaintenanceTypes (alias Pmt)
For example:
Pmt1 is base periodic maintenance and includes oil change + 5 checks,
Pmt2 is intermediate periodic maintenance and includes oil chage + 25 checks
FIELDS:
PmtCode (primary key)
PmtDescription (text field)
TABLE:
Checks
lists checks that can be included in one or mare periodic maintenance type
FIELDS:
CheckCode (primary key)
CheckDescription (text field)
TABLE: PmtChecks
relates tables Pmt to Checks
FIELDS: (all in primary key)
PmtCode
CheckCode
Now include in CarMaintenance reference to Pmt table by replacing field
PeriodicMaintenanceType by PmtCode.
Then, using Tools menu, establish relations between the tables to ensure
integrity:
CarMaintenance (PmtCode) --> PeriodicMaintenanceType (PmtCode)
PeriodicMaintenanceType (PmtCode --> PmtChecks (PmtCode)
Checks (CheckCode) --> PmtChecks (CheckCode)
Have fun!
"Jerry" <no*******@houston.rr.com> a écrit dans le message de news:
PT******************@tornado.texas.rr.com...
Hopefully this is the right group to ask. I am new to databases and I want
to build a database to record maintenance for my car to learn with. I
would appreciate any suggestions for fields to use for information I should
capture and should I make multiple tables or just one? Information
pointing me in a direction of ideas would be appreciated.
Thanks.