![]() |
Excel vs Access
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 |
"CyberTaz" wrote in message ... 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 |:) CyberTaz may be correct. If all you want to do is to insert data somewhere, Excel may very well be used. /Fredrik |
While I agree that a specific recommendation would be difficult for you-all
without more specifics, I do appreciate the all the help. From my vantage point, I am stuck in addressing the security issues for this project because I don't think I could competently put together a response to our IT folk who seem stuck on Access as an answer to everything. You're right that there are no "tables" to relate, in fact I am outlining the structure that I need in an Excel spreadsheet for the IT people to build from. It just seems to me that since this is a flat database that can be created in a spreadsheet, to be at the mercy of the 2 or 3 people in IT for any updates, new reports, etc. rather than the people who need to use the information seems wrong. Its just that I am a lone voice here and I have no reasonable solution to the security issue of multiple user access. If anyone has a suggestion within excel for that I am all ears. "CyberTaz" wrote: 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 |
All times are GMT +1. The time now is 07:03 PM. |
Powered by vBulletin® Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
ExcelBanter.com