mfg database design sugguestion.

[Guest]

Hi,

I am designing a mfg database and would like your expert sugguestions on
whether I should combine all the tables into one table or keep it separate
tables then use a union query to combine all the tables for report purposes.
The main report I would like to show is user enter the date (range) then the
report will show all the tables that have activities entered on those date
specified.

Here are my all my tables & data type. Thanks for any sugguestions
tbl_HelpID tbl_Date tbl_Author tbl_HelpType tbl_Description
tbl_Comments
AutoNumber Date/Time Number Text Text
Memo
tbl_MachID tbl_Date tbl_Author tbl_MachNumber tbl_Issue
tbl_Description
AutoNumber Date/Time Number Number Text Text
tbl_Responible tbl_EstDownTime tbl_Resolution tbl_Comments
Number Number Date/Time Memo

tbl_ManpowerID tbl_Date tbl_Author tbl_Operator tbl_Machine
tbl_Reason AutoNumber Date/Time Number Number Number
Text
tbl_Comments
Memo

tbl_MTOID tbl_Date tbl_Author tbl_PartID tbl_MachineID
tbl_Media
AutoNumber Date/Time Number Number Number Text
tbl_FWC tbl_Programmer tbl_StartDate tbl_EndDate
Text Number Date/Time Date/Time
tbl_Operator tbl_Description tbl_Comments
Number Text Memo

tbl_QualityID tbl_Date tbl_Author tbl_PartNumber tbl_TagNumber
AutoNumber Date/Time Number Number Text
tbl_SFC tbl_Reason tbl_Location tbl_Comments
Number Text Text Memo
tbl_PassdownID tbl_Date tbl_Author tbl_Machine tbl_Shift
AutoNumber Date/Time Number Number Text
tbl_Completed tbl_ToDoNext tbl_Comments
Text Text Memo

 

[Steve]

Tables should be designed indepently from displaying the data in forms aned
reports. Tables should be designed to follow the rules of normalization.
After the tables are designed, you then design queries to pull the data you
need for forms and reports from one or more sources.


PC Datasheet
Providing Customers A Resource For Help With Access, Excel And Word
Applications
(e-mail address removed)

 

[John Marshall, MVP]

and the last thing you do is even think about getting help from PCDatasheet.

I see your holiday from soliciting is over and you found a new victim in the
Access Tabledesign newsgroup.

John... Visio MVP

 

[StopThisAdvertising]

Tables should be designed

<snipped te rest >

Steve should behave ...
-
Hey Steve!! We don't need you here !!
Hey Steve!! We don't want you here !!

This is to inform 'newbees' here about PCD' Steve:
http://home.tiscali.nl/arracom/whoissteve.html (updated, mainly the 'abuse-reporting' page...)
Until now 4150+ pageloads, 2600+ first-time visitors
(these figures are real and rapidly increasing)

Why is this ???
Because Steve is the ONLY person here who continues to advertise in the groups.

It is not relevant whether he advertised in *this* particular post or not...
==> We want him to know that these groups are *not* his private hunting grounds!

For those who don't like too see all these messages:
==> Simply killfile 'StopThisAdvertising'.
Newbees will still see this warning-message.

ArnoR

 

[Michael Gramelspacher]

Except Steve's guidance this time seems appropriate.

The relational model allows and fosters the clear separation of
how a problem is modeled versus physical implementation details.
This is the relational concept of data independence. The solution
of a business problem should not be encumbered by anything that
detracts from the ability to clearly and precisely model it. This
is the essence of the concept of the logical model in relational
theory. -- Steve Dassin

 

[John Marshall, MVP]

It is a very basic DB Design 101 answer. So on it's on it sort of is OK, but
it lacks substance, but this is a ploy steve has used in the past. He
provides limited information and the OP then asks for more help. Steve then
takes it as a sign that he can ask the OP to contact him for more help at a
reasonable fee. For most people, this would be ignored, but early today
posted a direct solicitation in this group and shows no sign that he will
not continue

John... Visio MVP