Hi all,
i need to store data of measurments that were measured in a certain
date at a ship's main engine bearings.
- i have several ships
- each ship has one main engine made by a manufacturer with a uniq
model no. but that model can be exsists in several ships.
- each model of engine has several groups of bearings (i.e. main
bearings, thrust bearings etc.) and has several bearings of each
group. (i.e. main bearing no. 1, main bearing no. 2 etc.) here also a
group of bearings can be exsists in several engine models.

- each group of bearings with a bearing no. must have a manufacturer
minimum and maximum measurments for each group of bearings for each
bearing No.

- each group of bearings with a bearing no. must have an initial
measurement for each group of bearings for each bearing no. BUT, if
for an example ship no. 1 has an engine model x and ship no. 2 has
that same model, the initial measurement for the group of bearings for
the bearing number of each ship will be diferent measurement

- each group of bearings with a bearing no. has several points
(a,b,c,d etc.)where each point has its own measure BUT, sometime the
final measurement can be the measurement of point a and sometime the
final measurment can be a result of a calculating several points, for
an example the average measurement fot points a,b,c,d.

my question is as follow:

1. is it possible to built such a database in access (or any other
database) ?

2. if i have 29 ships, each one has 5 groups of bearings where each
group of bearing has about 15 measuring points and on average there
are 8 bearings of each group of bearings in an engine, can access hold
so much data (all are single, strings and long data types) ?

3. did someone has already design that kind of database and would like
to advise me and/or share some ideas ?

thanks in advance,
Alex g.

Yes you can put this data in access (or any other RDBMS). I think you
have a very good head start in the table design - ships, engine
manufactor, etc. and relationships between them. Probably the best
thing to do is get a blank page - sketch the data elements (ships,
bearings, etc.) link them but what they have in common. that would
give you the basic db/table design......once you have that it's
reviewing and coding......not sure how much ms access background you
have - if you need help let me know

alex (AT) oferb (DOT) co.il (Alex G) wrote in message news:<712510f3.0311050122.7bff7a3e (AT) posting (DOT) google.com>...

Alex:
The answer to one and two are yes.
There are a few minor complexities but nothing outrageous.
The size is trivial. At some point it might be wise to goto SQL
Server as the back end but not with 29 ships.
I haven't seen anything like this.

A major question you need to get straight in your own mind is:
What do you want to do with this thing once you have it?

To some degree the details of the design depend on the intended use.

Are you going to store only current measurments or do you want
history?
Do you want a report on all items where the change is greater than .25
mm?

The more you know about the intended use the better the initial design
will be.

Good Luck
Ira Solomon

On 5 Nov 2003 01:22:56 -0800, alex (AT) oferb (DOT) co.il (Alex G) wrote:

Hi Ira,
thanks your reply.
any how i managed to plan most of my tables in access. i all ready
designed and create most of the tables and established the
connections.
in that point i think the the best is for each vessel i will hold an
access database (as our vessels does not have servers on board there
for i can not install SQL server)but in our office i will create a
database on SQL server as we need to save data that will arrive from
our fleet to geather with manufacture data (minimum and maximum
measurments, trail measurments etc).
in case i'll have dificulties i'll will write. again thanks for your
assistance
rgds
Alex g


Ira Solomon <isolomon (AT) solomonltd (DOT) com> wrote