Access vs Excel

T

TAS

I'm trying to determine whether to use Access or Excel to accumulate and
report on research data. I'm very good with Excel and know that I can get
the info. I need with it, but wondering about using Access cuz the Excel file
will be getting big. Some basics on my research project:

One row (record) will have 195 cells (fields) of raw data. 192 will be
numerical that I need to sum and perform % of change calculations on.

About 1,000 records consisting of about 200 patients with about 5 records of
data for each from different time periods.

Ultimately need consolidated comparison data.

Two options. If this is all the data I have and this is a one-time project,
is Excel still worth using? If there is a possibility of repeating this
research project, does that make a difference? Any suggestions.
 
K

KC

I'm no expert by any means, but I'd say Access is the way to store your data.
At any time, you can export data from Access to perform calculations or
whatever it is you want Excel to do with it. I use the two in this way very
often.
 
T

Tom Wickerath

Hi TAS,

I agree with Kyle. However, Access does have a rather steep learning curve,
to use it correctly.

One statement that you made needs to be explored a bit:
One row (record) will have 195 cells (fields) of raw data. 192 will be
numerical that I need to sum and perform % of change calculations on.

A very common mistake when using Access is to import data from Excel
directly, without any thought to a process known as "normalization". In
essence, you end up with an Access spreadsheet (ie. you're guilty of
'committing spreadsheet' with Access). Most tables in relational databases
will not have more than 25 fields. To get the power of Access, and avoid all
kinds of headaches, you should normalize your data.

I have a Word document that I call Access Links.doc. You are welcome to
download a zipped copy from this location:

http://www.accessmvp.com/TWickerath/downloads/accesslinks.zip

The first three pages, along with two hyperlinks shown in red font on page
4, contain information that anyone using Access should become familiar with.
This includes avoiding the use of special characters, reserved words,
database design, best practices, etc. Do take a look at the first two
database design downloads on the Access Junkie's web site, written by
database design expert Michael Hernandez.
If there is a possibility of repeating this research project, does that make a difference?

Yes! You can put all of this data into one database (assuming you do not
exceed the 2 GB limit for a JET file--remember to compact your database as
needed: Tools | Database Utilities | Compact and repair database in Access
2003 and lower versions). Having all the data in one file will greatly ease
comparing results from one study to the next.


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

:

I'm no expert by any means, but I'd say Access is the way to store your data.
At any time, you can export data from Access to perform calculations or
whatever it is you want Excel to do with it. I use the two in this way very
often.

Kyle
__________________________________________

:

I'm trying to determine whether to use Access or Excel to accumulate and
report on research data. I'm very good with Excel and know that I can get
the info. I need with it, but wondering about using Access cuz the Excel file
will be getting big. Some basics on my research project:

One row (record) will have 195 cells (fields) of raw data. 192 will be
numerical that I need to sum and perform % of change calculations on.

About 1,000 records consisting of about 200 patients with about 5 records of
data for each from different time periods.

Ultimately need consolidated comparison data.

Two options. If this is all the data I have and this is a one-time project,
is Excel still worth using? If there is a possibility of repeating this
research project, does that make a difference? Any suggestions.
 
Å

å¡å†œçš„魔笛

很明显,ä½ çš„æ•°æ®é‡ä¸å°,用excelå¯èƒ½æ“作方便些,但ä¸é€‚åˆå¾ˆå¤šçš„æ•°æ®çš„æ“作.
access则是在æ“作上有些麻烦.如果ç¨å¾®ä¸“业些的è¯,access是好的选择.
如果有é…套程åºæ¥å®Œæˆæ•°æ®æ“作的è¯å°±æ›´å¥½äº†.
 
K

Ken Sheridan

Its impossible to be categorical about this on the basis of the brief outline
you've given, but I would counsel against assuming that a database would have
any advantage over a workbook. A relational database models the entity types
and the relationship types between them in whatever part of the real world it
deals with. Since the introduction of the relational model in 1970 it has
been shown to be a robust one with many applications.

As someone who has spent a career in environmental planning, databases have
been one of the major tools of my trade. However, workbooks have also been a
valuable resource in appropriate circumstances. Where a workbook really
scores is it the ease with which one can undertake statistical operations.
While I have, with colleagues from other scientific disciplines, undertaken
statistical analyses on various types of scientific data using Access this
has often meant programming the underlying mathematics. This can be quite
difficult when one is dealing with operations such as linear regression for
instance.

While data from Access tables can easily be exported to Excel for analysis,
and thus give you access (no pun intended!) to the statistical functions
which Excel supports, or indeed you can make direct use of those functions
within Access itself by returning a reference to the Excel object model,
there is little point in doing so if Access gives you no real benefit over
holding the data in an Excel workbook in the first place. If the data is in
essence just a set of numerical attribute values relating to a single entity
type, patients by the sound of it in your case, my gut feeling from my own
experience is that a workbook could well be a perfectly adequate mechanism,
with a database providing no real advantages, and the disadvantage of having
to learn the very different concepts which underlie a relational database
compared with those underlying a workbook (not that this would be wasted
effort, as I'm sure that once you do have a good understanding of the
relational database model you'll find plenty of applications for it). The
division of the data into 5 subsets for the different time periods can easily
be accommodated but having a worksheet for each in the workbook for the
research project. For repetition of the project you can firstly establish a
template in Excel and use that as the basis for each to avoid having to set
up the workbook from scratch each time.

An argument which can be put forward in favour of Access is that it is very
easy to set up a user interface in Access. However, in Excel one can set up
user forms of course to make for easy data input rather than entering it
directly into the cells. With your greater experience of Excel I'm sure you
know more about this than I as a relatively casual, albeit frequent user.

Finally while one can easily export data from Access to Excel, the reverse
is also true. As it happens I have a little demo, which I created for
colleagues, of how 'flat file' Excel data can be imported into Access and
recast into a set of normalized tables. If you are interested I can send you
a copy if you mail me at:

kenwsheridan<at>yahoo<dot>co<dot>uk

Ken Sheridan
Stafford, England
 
J

Jeff C

As an analyst working in corporate healthcare decision support I find little
to add to Ken's comments. Depending on the specific project I use both Excel
and Access interchangeably depending on what specific analysis is needed.

There are several reporting projects where I am using Access solely because
of its ability to automate with command line macros, making scheduling of
daily process very easy giving me daily reports that continuously update. By
using ODBC links to the database from within Excel you also get the best of
both depending on your outcome model.
 
T

TAS

Thank you.

KC said:
I'm no expert by any means, but I'd say Access is the way to store your data.
At any time, you can export data from Access to perform calculations or
whatever it is you want Excel to do with it. I use the two in this way very
often.
 
T

TAS

Thank you for the detailed response.

Tom Wickerath said:
Hi TAS,

I agree with Kyle. However, Access does have a rather steep learning curve,
to use it correctly.

One statement that you made needs to be explored a bit:


A very common mistake when using Access is to import data from Excel
directly, without any thought to a process known as "normalization". In
essence, you end up with an Access spreadsheet (ie. you're guilty of
'committing spreadsheet' with Access). Most tables in relational databases
will not have more than 25 fields. To get the power of Access, and avoid all
kinds of headaches, you should normalize your data.

I have a Word document that I call Access Links.doc. You are welcome to
download a zipped copy from this location:

http://www.accessmvp.com/TWickerath/downloads/accesslinks.zip

The first three pages, along with two hyperlinks shown in red font on page
4, contain information that anyone using Access should become familiar with.
This includes avoiding the use of special characters, reserved words,
database design, best practices, etc. Do take a look at the first two
database design downloads on the Access Junkie's web site, written by
database design expert Michael Hernandez.


Yes! You can put all of this data into one database (assuming you do not
exceed the 2 GB limit for a JET file--remember to compact your database as
needed: Tools | Database Utilities | Compact and repair database in Access
2003 and lower versions). Having all the data in one file will greatly ease
comparing results from one study to the next.


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

:

I'm no expert by any means, but I'd say Access is the way to store your data.
At any time, you can export data from Access to perform calculations or
whatever it is you want Excel to do with it. I use the two in this way very
often.

Kyle
__________________________________________

:

I'm trying to determine whether to use Access or Excel to accumulate and
report on research data. I'm very good with Excel and know that I can get
the info. I need with it, but wondering about using Access cuz the Excel file
will be getting big. Some basics on my research project:

One row (record) will have 195 cells (fields) of raw data. 192 will be
numerical that I need to sum and perform % of change calculations on.

About 1,000 records consisting of about 200 patients with about 5 records of
data for each from different time periods.

Ultimately need consolidated comparison data.

Two options. If this is all the data I have and this is a one-time project,
is Excel still worth using? If there is a possibility of repeating this
research project, does that make a difference? Any suggestions.
 
T

TAS

Thank you for your detailed response.


Ken Sheridan said:
Its impossible to be categorical about this on the basis of the brief outline
you've given, but I would counsel against assuming that a database would have
any advantage over a workbook. A relational database models the entity types
and the relationship types between them in whatever part of the real world it
deals with. Since the introduction of the relational model in 1970 it has
been shown to be a robust one with many applications.

As someone who has spent a career in environmental planning, databases have
been one of the major tools of my trade. However, workbooks have also been a
valuable resource in appropriate circumstances. Where a workbook really
scores is it the ease with which one can undertake statistical operations.
While I have, with colleagues from other scientific disciplines, undertaken
statistical analyses on various types of scientific data using Access this
has often meant programming the underlying mathematics. This can be quite
difficult when one is dealing with operations such as linear regression for
instance.

While data from Access tables can easily be exported to Excel for analysis,
and thus give you access (no pun intended!) to the statistical functions
which Excel supports, or indeed you can make direct use of those functions
within Access itself by returning a reference to the Excel object model,
there is little point in doing so if Access gives you no real benefit over
holding the data in an Excel workbook in the first place. If the data is in
essence just a set of numerical attribute values relating to a single entity
type, patients by the sound of it in your case, my gut feeling from my own
experience is that a workbook could well be a perfectly adequate mechanism,
with a database providing no real advantages, and the disadvantage of having
to learn the very different concepts which underlie a relational database
compared with those underlying a workbook (not that this would be wasted
effort, as I'm sure that once you do have a good understanding of the
relational database model you'll find plenty of applications for it). The
division of the data into 5 subsets for the different time periods can easily
be accommodated but having a worksheet for each in the workbook for the
research project. For repetition of the project you can firstly establish a
template in Excel and use that as the basis for each to avoid having to set
up the workbook from scratch each time.

An argument which can be put forward in favour of Access is that it is very
easy to set up a user interface in Access. However, in Excel one can set up
user forms of course to make for easy data input rather than entering it
directly into the cells. With your greater experience of Excel I'm sure you
know more about this than I as a relatively casual, albeit frequent user.

Finally while one can easily export data from Access to Excel, the reverse
is also true. As it happens I have a little demo, which I created for
colleagues, of how 'flat file' Excel data can be imported into Access and
recast into a set of normalized tables. If you are interested I can send you
a copy if you mail me at:

kenwsheridan<at>yahoo<dot>co<dot>uk

Ken Sheridan
Stafford, England
 
T

TAS

Unfortuantely your response did not come thru. I only got square like
characters. Thanks anyway.
 
T

TAS

Thank you for your detailed response.


Jeff C said:
As an analyst working in corporate healthcare decision support I find little
to add to Ken's comments. Depending on the specific project I use both Excel
and Access interchangeably depending on what specific analysis is needed.

There are several reporting projects where I am using Access solely because
of its ability to automate with command line macros, making scheduling of
daily process very easy giving me daily reports that continuously update. By
using ODBC links to the database from within Excel you also get the best of
both depending on your outcome model.
 
J

Jeffrey White

I would use Caboodle by Swink (http://www.swinklink.com). It doesn't require expert knowledge like Microsoft Excel and Access and can be shared with ease on the Internet for free. You can easily create data entry forms for your research and record as many records as you like. You can even export the records to excel or any other application when you are finished for further analysis.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top