How to map tables

Hi,
i am not able to design tables in an efficient way. Can any one help me
regarding table creation...Frist i wll explain the data to be stored.

An automobile company manufactures gaskets. for each gasket they wil assign a
part number. For each part thre could be multiple locations and each location
wil have the control limits. After manufacturing they will measure the each
part locations. i nedd to save the following information.
location ,measured value,
operator,--- name of the person who measured the value.
shift Id-- company runs in 3 shifts. so i need to indicate the shift ID (1,2,
3) for each location
check-- Either first Pc or lastPC
status--- is it ok or not....
comments- not ok then he has to enter comments.....
ReadingDate

all locations are measured by the same person,same shift ,check,date.

first i created a table named as MeasuredData contains the following fields
PartNumber,location ,measured value,
operator,shift Id,check,status,comments,ReadingDate

but the above table will contains the repeated data... So i decided to
maintain the data in 2 tables.
MeasuredData --- PartNumber,location ,measured value, ReadingDate
LocationMiscData--operator,shift Id,check,status,comments,ReadingDate (common
information)

But now i had some other problem....i.e. mapping... i have Date ,location
filters when user wants to view the data... i am not getting the view as
proper... if MeasuredData have 6 records then i am getting 18 records for
that date... so can u help me how can i oraganize my data......

Thanks in advance...

--
Message posted via http://www.accessmonster.com

How many gaskets would be checked in a single day? Two per shift – per
location?
Location 1
Shift 1
first Pc
lastPC
Shift 2
first Pc
lastPC
Shift 3
first Pc
lastPC
This is six items checked at a location in a day. Is this correct?


"bangaram via AccessMonster.com" wrote:

Hi,
i am not able to design tables in an efficient way. Can any one help me
regarding table creation...Frist i wll explain the data to be stored.

An automobile company manufactures gaskets. for each gasket they wil assign a
part number. For each part thre could be multiple locations and each location
wil have the control limits. After manufacturing they will measure the each
part locations. i nedd to save the following information.
location ,measured value,
operator,--- name of the person who measured the value.
shift Id-- company runs in 3 shifts. so i need to indicate the shift ID (1,2,
3) for each location
check-- Either first Pc or lastPC
status--- is it ok or not....
comments- not ok then he has to enter comments.....
ReadingDate

all locations are measured by the same person,same shift ,check,date.

first i created a table named as MeasuredData contains the following fields
PartNumber,location ,measured value,
operator,shift Id,check,status,comments,ReadingDate

but the above table will contains the repeated data... So i decided to
maintain the data in 2 tables.
MeasuredData --- PartNumber,location ,measured value, ReadingDate
LocationMiscData--operator,shift Id,check,status,comments,ReadingDate (common
information)

But now i had some other problem....i.e. mapping... i have Date ,location
filters when user wants to view the data... i am not getting the view as
proper... if MeasuredData have 6 records then i am getting 18 records for
that date... so can u help me how can i oraganize my data......

Thanks in advance...

--
Message posted via http://www.accessmonster.com

How many gaskets would be checked in a single day? Two per shift – per
location?
Location 1
Shift 1
first Pc
lastPC
Shift 2
first Pc
lastPC
Shift 3
first Pc
lastPC
This is six items checked at a location in a day. Is this correct?


"bangaram via AccessMonster.com" wrote:

Hi,
i am not able to design tables in an efficient way. Can any one help me
regarding table creation...Frist i wll explain the data to be stored.

An automobile company manufactures gaskets. for each gasket they wil assign a
part number. For each part thre could be multiple locations and each location
wil have the control limits. After manufacturing they will measure the each
part locations. i nedd to save the following information.
location ,measured value,
operator,--- name of the person who measured the value.
shift Id-- company runs in 3 shifts. so i need to indicate the shift ID (1,2,
3) for each location
check-- Either first Pc or lastPC
status--- is it ok or not....
comments- not ok then he has to enter comments.....
ReadingDate

all locations are measured by the same person,same shift ,check,date.

first i created a table named as MeasuredData contains the following fields
PartNumber,location ,measured value,
operator,shift Id,check,status,comments,ReadingDate

but the above table will contains the repeated data... So i decided to
maintain the data in 2 tables.
MeasuredData --- PartNumber,location ,measured value, ReadingDate
LocationMiscData--operator,shift Id,check,status,comments,ReadingDate (common
information)

But now i had some other problem....i.e. mapping... i have Date ,location
filters when user wants to view the data... i am not getting the view as
proper... if MeasuredData have 6 records then i am getting 18 records for
that date... so can u help me how can i oraganize my data......

Thanks in advance...

--
Message posted via http://www.accessmonster.com

Per day they have to manufacture limited gaskets like 10k per day or it
varies based on the production. They wil measure the first piece of the
production and last piece of the production. So it can be shift 1 or 2 or 3.
All locations are measured at the same time and locations for each part
should be different.
For example.
Part:0102-07645-BR1
Location1 ,location2....LocationN
Shift 1 First PC
Shift 1 LastPC.

Part:0102-07645-BR2
Location1 ,location2....LocationN
Shift 1 First PC
Shift 2 or 3 LastPC.

Measurements can be taken only for the first piece and the last piece...
KARL DEWEY wrote:
How many gaskets would be checked in a single day? Two per shift – per
location?
Location 1
Shift 1
first Pc
lastPC
Shift 2
first Pc
lastPC
Shift 3
first Pc
lastPC
This is six items checked at a location in a day. Is this correct?

Hi,
i am not able to design tables in an efficient way. Can any one help me
[quoted text clipped - 31 lines]

Thanks in advance...

--
Message posted via http://www.accessmonster.com

Here is how I see your table structure --
Table: LocationMiscData
Name Type Size
LocationDataID Long Integer 4
Part_No Text 50
Location Text 50
ReadingDate Date/Time 8

Table: MeasuredData
Name Type Size
LocationDataID Long Integer 4
Operator Text 50
Shift Long Integer 4
PC Text 50
Measured value Single 4
Pass Yes/No 1
Comments Text 255

Set the relationship between the tables. Use a form with subform for data
entry. The Master/Child link between them will be the LocationDataID. The
subform in datasheet view.

"bangaram via AccessMonster.com" wrote:

Per day they have to manufacture limited gaskets like 10k per day or it
varies based on the production. They wil measure the first piece of the
production and last piece of the production. So it can be shift 1 or 2 or 3.
All locations are measured at the same time and locations for each part
should be different.
For example.
Part:0102-07645-BR1
Location1 ,location2....LocationN
Shift 1 First PC
Shift 1 LastPC.

Part:0102-07645-BR2
Location1 ,location2....LocationN
Shift 1 First PC
Shift 2 or 3 LastPC.

Measurements can be taken only for the first piece and the last piece...
KARL DEWEY wrote:
How many gaskets would be checked in a single day? Two per shift – per
location?
Location 1
Shift 1
first Pc
lastPC
Shift 2
first Pc
lastPC
Shift 3
first Pc
lastPC
This is six items checked at a location in a day. Is this correct?

Hi,
i am not able to design tables in an efficient way. Can any one help me
[quoted text clipped - 31 lines]

Thanks in advance...

--
Message posted via http://www.accessmonster.com

hi,
I think this table structure still maitaining the reduntant information. For
example
Part_ID is 0102-07645-BR1 and locations are J a Hght,J b Hght,J c Hght,J a
wdth,J b wdth,J c wdth and so on...

Measurement on 3/8/2006 is as follows
Inspector ReadingDate Shift PC J a Hght J b Hght J c Hght J a wdth J b
wdth J c wdth ......
Gemini 3/8/2006 1 FP 0.034 0.045 0.056
0.023 0.067 0.048
Gemini 3/8/2006 2 LP 0.037 0.050 0.045
0.013 0.072 0.068

This could be saved in the tables as follows.....
LocationMiscData
0000001 0102-07645-BR1 J a Hght 3/8/2006
0000002 0102-07645-BR1 J b Hght 3/8/2006
0000003 0102-07645-BR1 J c Hght 3/8/2006 and so on....

MeasuredData
0000001 Gemini 1 FP 0.034 yes ok
0000002 Gemini 1 FP 0.045 yes ok
0000003 Gemini 1 FP 0.056 yes ok... For each location i have to store
like this...Number locations can be 50... For only FirstPC u have to
maintain 50 records with the same information...There is no limit on the
number of locations.. he can have as many as he want..... is it good one?

KARL DEWEY wrote:
Here is how I see your table structure --
Table: LocationMiscData
Name Type Size
LocationDataID Long Integer 4
Part_No Text 50
Location Text 50
ReadingDate Date/Time 8

Table: MeasuredData
Name Type Size
LocationDataID Long Integer 4
Operator Text 50
Shift Long Integer 4
PC Text 50
Measured value Single 4
Pass Yes/No 1
Comments Text 255

Set the relationship between the tables. Use a form with subform for data
entry. The Master/Child link between them will be the LocationDataID. The
subform in datasheet view.

Per day they have to manufacture limited gaskets like 10k per day or it
varies based on the production. They wil measure the first piece of the
[quoted text clipped - 32 lines]

Thanks in advance...

--
Message posted via http://www.accessmonster.com