Hello to all of you
I'm reading lots of your post to try to find a hint of how I could structure my database. But can't quite find something that will allow me to start in a structured way. Let me first explain what is the goal of the database and what it will be doing :
The database is to create an estimate on project that we could do at my work. Let me show you what it will do as a finished result and the global architecture of the db
1- Estimation #1 Name X
a) Phase 1 to X of the project
i)Field ( Mecanic, civil, piping,....etc]
1.Subfield ( each field has it's own subfield ex: civil-> demolition, excavation...)
a. Items : I want to put a form that will vary accordingly with the field
ex: for piping, user chooses what he want to add (Pipe/fitting/welding/valve/..) then he adds the info that vary accordingly to to his choice (ex: for pipe=> he enters spec define from company chosen by user, diameter, length)
Up to know I've been gathering the information in all the sources around me for the Piping ( consider to be the harder because it uses lots of tables, I assume that when I'm able to do the piping I'll be able to modify it to the other fields)
About the informations I have to enter, I'm confused in how I should enter it because everything is related in one way or an other. For instance lets take the table of pipe specs.
to start I have to tell you that every company has its own specs so I have to list every detail of the spec need for calculation after. Here is how it's in a excel file :
________________| spec 1|spec2|.....__________________________
small pipe material_|(linked to a list in case any change occure in spec)
pype type________|(linked to a list in case any change occure in spec)
minimum schedule__| Fixed for a spec but linked to a table
Connection type___|(linked to a list in case any change occure in spec)
maximum diameter__|Fixed for a spec should I link it to a table?
Flange type_______|(linked to a list in case any change occure in spec)
Flange class______| Fixed for a spec should I link it to a table?
the field schedule could have numerical values or not. When not numerical it should go on a table and convert it to numerical accordingly to the diameter entered.
the table is repeted for medium, large and xlarge pipes determined by the maximum diameter field.
When a estimator enters a line, the form looks at the data entered and calculates with different tables the cost and man/hour cost. But accordingly to his choise of company, a correction factor must be inserted and the labor cost is different for each company.
The estimator can also deactivate a phase if he chooses not to do it.
The field will by predetermined by the choises the estimator does but could be changed if it needs customization.
This is for a 1 user use (one at a time)but I think it would be better to separate the tables from the forms, query .... because updates could be added in the server and each user could go and download the data without having to download all the program again.
I consider myself as a beginner in db and it's my first from the ground up. I'll receive a access 2003 bible soon to help me with the work and the internet is my new friend. I have 4 months to do it, at 40+ hours a week. Do you think I'll be able to finish?
I guess my main question is how could I design my database so it's easily upgradable to add more fields if I don't have time to finish...
thank you very much for your time and hoping you'll be able to guide me in creating a well designed database
Bruno
I'm reading lots of your post to try to find a hint of how I could structure my database. But can't quite find something that will allow me to start in a structured way. Let me first explain what is the goal of the database and what it will be doing :
The database is to create an estimate on project that we could do at my work. Let me show you what it will do as a finished result and the global architecture of the db
1- Estimation #1 Name X
a) Phase 1 to X of the project
i)Field ( Mecanic, civil, piping,....etc]
1.Subfield ( each field has it's own subfield ex: civil-> demolition, excavation...)
a. Items : I want to put a form that will vary accordingly with the field
ex: for piping, user chooses what he want to add (Pipe/fitting/welding/valve/..) then he adds the info that vary accordingly to to his choice (ex: for pipe=> he enters spec define from company chosen by user, diameter, length)
Up to know I've been gathering the information in all the sources around me for the Piping ( consider to be the harder because it uses lots of tables, I assume that when I'm able to do the piping I'll be able to modify it to the other fields)
About the informations I have to enter, I'm confused in how I should enter it because everything is related in one way or an other. For instance lets take the table of pipe specs.
to start I have to tell you that every company has its own specs so I have to list every detail of the spec need for calculation after. Here is how it's in a excel file :
________________| spec 1|spec2|.....__________________________
small pipe material_|(linked to a list in case any change occure in spec)
pype type________|(linked to a list in case any change occure in spec)
minimum schedule__| Fixed for a spec but linked to a table
Connection type___|(linked to a list in case any change occure in spec)
maximum diameter__|Fixed for a spec should I link it to a table?
Flange type_______|(linked to a list in case any change occure in spec)
Flange class______| Fixed for a spec should I link it to a table?
the field schedule could have numerical values or not. When not numerical it should go on a table and convert it to numerical accordingly to the diameter entered.
the table is repeted for medium, large and xlarge pipes determined by the maximum diameter field.
When a estimator enters a line, the form looks at the data entered and calculates with different tables the cost and man/hour cost. But accordingly to his choise of company, a correction factor must be inserted and the labor cost is different for each company.
The estimator can also deactivate a phase if he chooses not to do it.
The field will by predetermined by the choises the estimator does but could be changed if it needs customization.
This is for a 1 user use (one at a time)but I think it would be better to separate the tables from the forms, query .... because updates could be added in the server and each user could go and download the data without having to download all the program again.
I consider myself as a beginner in db and it's my first from the ground up. I'll receive a access 2003 bible soon to help me with the work and the internet is my new friend. I have 4 months to do it, at 40+ hours a week. Do you think I'll be able to finish?
I guess my main question is how could I design my database so it's easily upgradable to add more fields if I don't have time to finish...
thank you very much for your time and hoping you'll be able to guide me in creating a well designed database
Bruno
