Repost hopefully with attached image

Hello fellow Access users,

I have attached my relationship schema to a maintenance database that I have
put together quickly.
It's been a while since I did any access creation here in Australia since my
Tech College years.oh about 1998 I guess.
I used to frequent these newsgroups back then and I can fondly remember the
name John Vinson during that period helping me out, so it's great to see you
still around John.
Anyway back to my question, I was just wanting to know if there is anything
I may have missed in my quick creation of the tables for this maintenance db
and further to the referential integrity of my relationship diagram, before
I continue further with it.

I intend using replication functionality which I have to yet learn.


Kind Regards
Doug Marriott

While I'll readily admit that I don't know the business you're modelling,
your tables look very suspect to me.

With tblMaintenance having fields with names like "Engine", "Transmission",
"FrontEnd" means you're "hiding" information in the field names. Same
comment about tblMaintenanceTask having fields with names like "EngineWork",
"TransmissionWork", "FrontEndWork". In both cases, the recommendation would
be to have "narrower" tables: one field that stores the type of data
("Engine", "Transmission") and another field that stores the value, so that
you'd have multiple rows, not multiple columns.

tblMaintenance is linked in a one-to-many with tblEquipment. That means that
if you've got multiple similar pieces of equipment, you'll probably have
multiple similar rows in tblMaintenance. As I said, I don't know your
situation, but I would think that you'd have a many-to-many relationship
between Equipment and Maintenance (this type of equipment requires multiple
maintenance tasks, this maintenance task is performed on multiple pieces of
equipment)

You should rename the Date field in tblMaintenance. Date is a reserved word,
and should never be used for your own purposes. For a comprehensive list of
names to avoid (as well as a link to a free utility to check your
application for conformance), see what Allen Browne has at
http://www.allenbrowne.com/Ap****ueBadWord.html

I'd also strongly recommend renaming the field Serial/Rego/Vin in
tblEquipment: special characters like slashes (or spaces) aren't a good
idea.

It might be worth checking whether there's something relevant to your task
at http://www.databaseanswers.org/data_models/index.htm

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)


"Doug Marriott" wrote in message
...
Hello fellow Access users,

I have attached my relationship schema to a maintenance database that I
have
put together quickly.
It's been a while since I did any access creation here in Australia since
my
Tech College years.oh about 1998 I guess.
I used to frequent these newsgroups back then and I can fondly remember
the
name John Vinson during that period helping me out, so it's great to see
you
still around John.
Anyway back to my question, I was just wanting to know if there is
anything
I may have missed in my quick creation of the tables for this maintenance
db
and further to the referential integrity of my relationship diagram,
before
I continue further with it.

I intend using replication functionality which I have to yet learn.


Kind Regards
Doug Marriott

On Tue, 2 Dec 2008 21:51:14 +1100, "Doug Marriott"
wrote:

Hello fellow Access users,

I have attached my relationship schema to a maintenance database that I have
put together quickly.
It's been a while since I did any access creation here in Australia since my
Tech College years.oh about 1998 I guess.
I used to frequent these newsgroups back then and I can fondly remember the
name John Vinson during that period helping me out, so it's great to see you
still around John.
Anyway back to my question, I was just wanting to know if there is anything
I may have missed in my quick creation of the tables for this maintenance db
and further to the referential integrity of my relationship diagram, before
I continue further with it.

I intend using replication functionality which I have to yet learn.


Kind Regards
Doug Marriott


Hi Doug! Thanks for the kind words (that's back in the Compuserve era...
sheesh! Making me feel old!)

We'll let you off this time... but posting binaries in this Text group is
somewhat frowned upon. Some folks, especially overseas, have to pay by the
byte for all downloads.

Read Douglas' suggestions for normalization - he's quite right as usual, and I
have nothing to add.
--

John W. Vinson [MVP]