Convert Execl Spreadsheet to Access

[cadonn]

Hi, I am really new to using MS Access so would appreciate any
suggestions. have a purchase order spreadsheet in Excel with the
following column headings

Date, Name of User, PO Number, Org Code, Product, Cost, Comments

I would like to convert this into Acess 2003 without having to retype
all of it. Right now we have several people accessing the PO
spreadsheet and since only one person can access at a time, it is
becoming a pain. We have to contact the users and ask if they are
finished with the PO spreadsheet. I figured with access, more than
one person can be entering data at the same time as the PO number
would be set as the primary.

Am I understanding this correctly? Or should I be looking at
additional software to complete this task.

Thank you.

Cate

 

[Keith Wilby]

Hi, I am really new to using MS Access so would appreciate any
suggestions. have a purchase order spreadsheet in Excel with the
following column headings

Date, Name of User, PO Number, Org Code, Product, Cost, Comments

I would like to convert this into Acess 2003 without having to retype
all of it. Right now we have several people accessing the PO
spreadsheet and since only one person can access at a time, it is
becoming a pain. We have to contact the users and ask if they are
finished with the PO spreadsheet. I figured with access, more than
one person can be entering data at the same time as the PO number
would be set as the primary.

Am I understanding this correctly?

Yes and no. You can import your data into a table fairly easily but there
are other considerations, the first of which should be to split the database
and provide each user with their own front end file. This would entail your
having to design forms for data manipulation and maybe even hiding the db
window from your users. Have a look at this for starters:

http://www.granite.ab.ca/access/splitapp/overview.htm

Keith.
www.keithwilby.com

 

[BruceM]

Another consideration is that it would be incorrect to regard Access as a
sort of multi-user spreadsheet program. It is a tool to create a relational
database. As such, each entity should be in its own table. In a typical PO
database you would have something like a vendor table, a purchase order
table, a line items table, and a users table to serve as a lookup for
entering the user's name into the PO. A search for Purchase Order database
systems (or something of the sort) should provide some additional
information.

 

[cadonn]

Thank you Keith. That does look a little complicated for my
experience. I will have a closer look and maybe look at tutorials.

Cate