A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Database Design
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Help with creating database



 
 
Thread Tools Display Modes
  #1  
Old March 8th, 2010, 08:41 PM posted to microsoft.public.access.tablesdbdesign
Phil S.
external usenet poster
 
Posts: 1
Default Help with creating database

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
  #2  
Old March 8th, 2010, 09:05 PM posted to microsoft.public.access.tablesdbdesign
KARL DEWEY
external usenet poster
 
Posts: 10,767
Default Help with creating database

Would it make more sense to have a separate database for each? Or just one
database for all?
One database with a field in your table that is related to a client table so
for data entry the person select client instead of typing each time to avoid
typos.

You did not say how your data was to be used or how often.

You did not say how Style, descriptions, testing status, shipping
information, fitting
information, etc. is expressed in you 'report'.

--
Build a little, test a little.


"Phil S." wrote:

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

  #3  
Old March 8th, 2010, 09:20 PM posted to microsoft.public.access.tablesdbdesign
Phil S.[_2_]
external usenet poster
 
Posts: 1
Default Help with creating database

I didn't want to be too specific in my first post, as the report can be a
little complicated, but I'll outline the fields below: (each group of fields
falls into a different category or department that is responsible for the
information)

Group Name = Delivery Time Period (ie. May/June)
Style Number = Identifies product (ie. 000123)
Description = Product Summary (ie. V-Neck Tank Top)
Color = Color (ie. Sky Blue)

Cut Ticket# = Order number for factory to create goods (ie. 100012)
Quantity = Number of units
Issue Date = Date when ticket was issued.

Customer PO# = ie. 123456
PO Quantity = quantity ordered from customer
PO date = date ordered

Fabric at factory = date arrived
Approval = date fabric approved
Test = date fabric tested
Inspection = date fabric inspected

Etc, etc, etc.

This information is constantly looked at and updated over a period of weeks
to months. Every few months is a different season and these orders are
generally per season. So the entire order is tracked over a couple months,
and then onto a new order, and new report.

I would like for each department of the company to be able to input their
"piece of the pie," or report through a customized form. In the end the
entire report would be pieced together and viewable as a whole.

"KARL DEWEY" wrote:

You did not say how your data was to be used or how often.

You did not say how Style, descriptions, testing status, shipping
information, fitting
information, etc. is expressed in you 'report'.

--
Build a little, test a little.


"Phil S." wrote:

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

  #4  
Old March 8th, 2010, 10:13 PM posted to microsoft.public.access.tablesdbdesign
Marco[_6_]
external usenet poster
 
Posts: 11
Default new messenger

Friends and friends around the world.
We are presenting the new messenger.
He will be in the commissioning by the friends that we indicate to use the
system.
Access the system by clicking the link below and register free.

You get something for using orkut?
You get something for using skype?
You gain something by using twiter?
You get algumaocisa for using facebook?

Enjoy this is your time!!

Sign up and join for free.


http://www.sqipcom.com/?ref=webempreendedor

http://stakeholder.sqipcom.com/user/webempreendedor



 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 07:01 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.