Advice on whether to use Excel vs. Access to create a company database

**RoyMakaay1985** · 09-01-2009, 10:37 AM

Hi,

I am looking for advice on a project, that I am currently working on. The big question is, whether to use MS Access or MS Excel. Some facts:
- The task is to create a database for customer acquisition projects. The data will be updated weekly, but is small in size (~20 entries/week). Projects can change their status (offer made - contract signed - rejected - etc.).
- It is desired to use the data for numerous queries (customer, type of project, revenue, employee, etc., year, date).
- I have no experience with Access, but quite some with MS Excel. There is no Access database in use in the company so far, but Excel is used frequently.

I would be happy to receive some thoughts of experienced users, that have worked with both programs.

The Version will be Access 2002 resp. Excel 2002.

Thanks in advance!

**split_atom18** · 09-01-2009, 11:20 AM

Since I could see something like this continuing to expand with more and more features. I would recommend using access.

How many people would be accessing this database? (At one time?)

Will you need reports for this data, and how many?

Do all the computers in your business have access?(not that important as runtime will work)

Do they all have excel?

Just some questions,

Dan

**RoyMakaay1985** · 09-02-2009, 04:18 AM

In total, about 50 people would access the database, but I assume, there will usually only be one person editing data at a time (as I said, only about 20 entries per week)

Reports will be necessary for both every user (showing only the user's own projects), the team leader (standardized report every week, filtering necessary for employee, revenue, type of project) and the executive manager (to achieve an overview over all projects, filtering for whatever he's interested in)

All Computers in the business have both Excel and Access

Thanks already for your help!

**split_atom18** · 09-02-2009, 09:08 AM

Based on the answers you gave me, I would highly suggest access. If you need help we are here!!!

Good Luck

Dan

**RoyMakaay1985** · 09-02-2009, 10:52 AM

If you need help we are here!!!

Ok, I'll give it (a tutorial) a try... Here you go

**split_atom18** · 09-02-2009, 11:53 AM

Originally Posted by RoyMakaay1985

Ok, I'll give it (a tutorial) a try... Here you go

Posted on that one.

**crazysniper** · 09-03-2009, 11:19 AM

Im not sure how big the company is, and what data will be stored in your database, but i have to let you know that MS Access is only capable of holding up to 2GB of data. If you think you'll be storing more than this over time. I would suggest using SQL.

**split_atom18** · 09-03-2009, 11:23 AM

Originally Posted by crazysniper

Im not sure how big the company is, and what data will be stored in your database, but i have to let you know that MS Access is only capable of holding up to 2GB of data. If you think you'll be storing more than this over time. I would suggest using SQL.

Originally Posted by RoyMakaay1985

In total, about 50 people would access the database, but I assume, there will usually only be one person editing data at a time (as I said, only about 20 entries per week)

Access provides features to convert to SQL if it does get to big. 2GB of data is a lot in text. Also with SQL you can still use an Access Front End.