Sorry...

Like i said the original table has more than 100 columns, so i'll put here a sample of one similar with less columns.

Let's say that the company manufactures products for sale, when i say manufacture i say all the stages. Start in the design (2D design department), approve the design (another department), modeling (3D department), send to factory (factory department).

For each department i have to have some common properties, the accepted bit, rejected bit, accepted date, rejected date, accepted by, rejected by, number of rejections, expected send date (to another department), who sent, sent bit.

Now some differences, from the 2D design to approve the users should add some drawings (paths), from modeling to factory the user must indicate the time that the product will take to be manufactured, in the factory the users that work in the product must write how much time it takes for each operation (cutting, soldering, etc.).

Product Table (simplified version)

id

Name

HasDrawings (a related table by the id)

UserSentToApprove

DateSentToApprove

---- Common to the Sections ---

Accepted

Rejected

AcceptedBy

AcceptedDate

RejectedBy

RejectedDate

NumRejections

Sent

ExpectedSendDate

SendDate

------ I have the above columns duplicated for evey section with different names ---

---- Modeling Section ----

TimeToDelivery

---- Factory Section ----

TimeToCut

TimeToSolder

TimeToAssemble

TimeToWhatever

----- Some General ---

Finished

Discarded

Removed

I have more columns, but for the purpose of explain my problem, i think this's enough. 🙂

Thanks