P
Phil S.
I'm a recent college graduate at a new job. I am trying to help my company
move a report that is currently done in Excel into Access.
To help you better understand my goal I will try to describe my business and
the nature of this report as briefly as possible.
We are a clothing designer. All of our product is produced in factories
overseas and delievered to our clients in the U.S.
Our W.I.P. report is currently in Excel. It's purpose is to give us an
up-to-date picture of what part of the production line our products are
currently in. Information on this report includes Style names and
descriptions; Fabric testing status; shipping information; fitting
information; etc. All of this information is gathered and input to an Excel
spreadsheet. The spreadsheet can get big, and become difficult to navigate or
read. The major problem is that each piece of information comes from
different departments and is re-entered by the people in charge of managing
the report. This leaves too much room for error.
My idea is to create a database where each category of information is
divided by department. I would like to have simple forms that each department
is responsible for entering their data into. Rather than having one person or
department fetch all of this data.
The only important stipulation is that the records need to be able to be
sorted Shipping dates and style#.
We also have multiple clients. Would it make more sense to have a separate
database for each? Or just one database for all?
I'm new to access, but am a quick learner. I would appreciate very much if
anyone can help walk me through the basic fundamentals and concepts of how a
database like this could be designed.
Thanks,
Phil
move a report that is currently done in Excel into Access.
To help you better understand my goal I will try to describe my business and
the nature of this report as briefly as possible.
We are a clothing designer. All of our product is produced in factories
overseas and delievered to our clients in the U.S.
Our W.I.P. report is currently in Excel. It's purpose is to give us an
up-to-date picture of what part of the production line our products are
currently in. Information on this report includes Style names and
descriptions; Fabric testing status; shipping information; fitting
information; etc. All of this information is gathered and input to an Excel
spreadsheet. The spreadsheet can get big, and become difficult to navigate or
read. The major problem is that each piece of information comes from
different departments and is re-entered by the people in charge of managing
the report. This leaves too much room for error.
My idea is to create a database where each category of information is
divided by department. I would like to have simple forms that each department
is responsible for entering their data into. Rather than having one person or
department fetch all of this data.
The only important stipulation is that the records need to be able to be
sorted Shipping dates and style#.
We also have multiple clients. Would it make more sense to have a separate
database for each? Or just one database for all?
I'm new to access, but am a quick learner. I would appreciate very much if
anyone can help walk me through the basic fundamentals and concepts of how a
database like this could be designed.
Thanks,
Phil