By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,808 Members | 1,477 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,808 IT Pros & Developers. It's quick & easy.

make database

P: n/a
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.
May 19 '06 #1
Share this Question
Share on Google+
3 Replies


P: n/a
On Fri, 19 May 2006 22:45:03 GMT, "Jerry" <no*******@houston.rr.com>
wrote:

File > New
Check out the various template databases available. With Access 2003
there also are templates online. One of them may suit your needs or
could be used as a starting point.

-Tom.
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.


May 20 '06 #2

P: n/a
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.

May 21 '06 #3

P: n/a

"Michel" <mi***********@yahoo.ca> wrote in message
news:pq*********************@wagner.videotron.net. ..
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.



Ok, I am having fun. But not a lot of success. I could not find a template
that looked useful so I am starting from scratch. What I have so far is
something like this:

Table: Maintenance
ServicedBy
ServiceDate
WorkPerformed
Odometer
PartsUsed
Parts Cost

What I am thinking is I would like to list the parts individually and the
cost of each part used if more than one at time of service instead of a lump
of them in the same field. Make sense?

Thanks
May 21 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.