Is there a good criteria that one could use to determine whether data should
be put into a sophisticated excel spreadsheet or an Access database? I am
trying to determine the best location for a new statistical project I am
working on.

Thanks!

Amy

"cvgairport" wrote in message
...
Is there a good criteria that one could use to determine whether data
should
be put into a sophisticated excel spreadsheet or an Access database? I am
trying to determine the best location for a new statistical project I am
working on.

Thanks!

Amy


First of all, Excel isn't really a database. I suspect you will run into all
kinds of problems if you want more than one user. Tell us a tad more about
the project.

/Fredrik

Yes, there would be more than one user but I am having trouble with what
Access brings to the table that Excel can't. The project is the collection
of static information arranged in accounts on the rows and months accross the
top. There will be summations and calculations that need to be done with the
inputted data and reporting done off of the information. I mean I know that
Access can do all that but what is it that Excel can't do that Access can.


"Fredrik Wahlgren" wrote:


"cvgairport" wrote in message
...
Is there a good criteria that one could use to determine whether data
should
be put into a sophisticated excel spreadsheet or an Access database? I am
trying to determine the best location for a new statistical project I am
working on.

Thanks!

Amy


First of all, Excel isn't really a database. I suspect you will run into all
kinds of problems if you want more than one user. Tell us a tad more about
the project.

/Fredrik

"cvgairport" wrote in message
...
Yes, there would be more than one user but I am having trouble with what
Access brings to the table that Excel can't. The project is the
collection
of static information arranged in accounts on the rows and months accross
the
top. There will be summations and calculations that need to be done with
the
inputted data and reporting done off of the information. I mean I know
that
Access can do all that but what is it that Excel can't do that Access can.



Lots of things. In Excel, you can't really force a column to hold only a
certain type of information. Excel sheets are not very safe, the sheet may
become corrupt. Excel is most likely very slow, there are no indexes.
Withoout constraints, there's no way to guarantee that there are no
duplicate data. Whenever two users try to access the same data, you will
probably run into all kinds of problems. A good alternative to Access is
MSDE which you may want to consider.

/Fredrik

What is MSDE?

"Fredrik Wahlgren" wrote:


"cvgairport" wrote in message
...
Yes, there would be more than one user but I am having trouble with what
Access brings to the table that Excel can't. The project is the
collection
of static information arranged in accounts on the rows and months accross
the
top. There will be summations and calculations that need to be done with
the
inputted data and reporting done off of the information. I mean I know
that
Access can do all that but what is it that Excel can't do that Access can.



Lots of things. In Excel, you can't really force a column to hold only a
certain type of information. Excel sheets are not very safe, the sheet may
become corrupt. Excel is most likely very slow, there are no indexes.
Withoout constraints, there's no way to guarantee that there are no
duplicate data. Whenever two users try to access the same data, you will
probably run into all kinds of problems. A good alternative to Access is
MSDE which you may want to consider.

/Fredrik

"cvgairport" wrote in message
...
What is MSDE?

"Fredrik Wahlgren" wrote:



It's the desktop version of SQL Server. It's very good but it doesn't come
with Administration tools. I guess it could be overkill for you but that
really depends on the complexity of the database you need.

http://www.microsoft.com/sql/msde/default.asp

/Fredrik

It's impossible to make a responsible suggestion without alot more info, but
based on what you posted Access & MSDE may very well be overkill.

If your list of records does not actually consist of several different types
of records that must "relate" to one another (eg., Customers & Employees &
Products & Vendors & Sales Transactions...) Excel is *probably* the better
choice for computations, statistical analysis, etc.

IMHO, the major shortcoming of Excel in the context of your posts is the
lack of sophisticated Reporting features. That may not be a problem, and can
be handled other software (Word, Crystal Reports & many others) if it is.

Good Luck |:)

"cvgairport" wrote:

What is MSDE?

"Fredrik Wahlgren" wrote:


"cvgairport" wrote in message
...
Yes, there would be more than one user but I am having trouble with what
Access brings to the table that Excel can't. The project is the
collection
of static information arranged in accounts on the rows and months accross
the
top. There will be summations and calculations that need to be done with
the
inputted data and reporting done off of the information. I mean I know
that
Access can do all that but what is it that Excel can't do that Access can.



Lots of things. In Excel, you can't really force a column to hold only a
certain type of information. Excel sheets are not very safe, the sheet may
become corrupt. Excel is most likely very slow, there are no indexes.
Withoout constraints, there's no way to guarantee that there are no
duplicate data. Whenever two users try to access the same data, you will
probably run into all kinds of problems. A good alternative to Access is
MSDE which you may want to consider.

/Fredrik