-
If you would like to post, please check out the MrExcel Message Board FAQ and register here. If you forgot your password, you can reset your password.
Access vs Excel
- Thread starter colmmc
- Start date
Well, you can easily create queries on your data and display the results in forms and reports, you can use forms for data input and Access validation is much more robust than Excel's. Is there something in particular you want to do?
Upvote
0
Nothing in particular. I am well versed in Excel but I'm only starting to teach myself Access. I can use excel to do most things that I am led to believe Access can do.
I know, at this moment in time, I do not know alot about Access so there may be, and probably will be, lots of functions that I am not aware of. That's why I ask.
Forgive my naivity and ignorance.
I know, at this moment in time, I do not know alot about Access so there may be, and probably will be, lots of functions that I am not aware of. That's why I ask.
Forgive my naivity and ignorance.
Upvote
0
I guess the best way is to just play around with Access in the same way as you got to know Excel. I generally use Access (or SQL Server with an Access front-end) when I need to handle large volumes of data, possibly input by multiple users and need the extra security and ease of displaying different views of the data that a database offers.
BTW, I wasn't trying to have a go at you, I just wondered if there was something in particular you needed to do that was difficult to implement in Excel. There's no stupid or naive questions, but the board is generally more suited to specific enquiries rather than a broad-brush one
.
BTW, I wasn't trying to have a go at you, I just wondered if there was something in particular you needed to do that was difficult to implement in Excel. There's no stupid or naive questions, but the board is generally more suited to specific enquiries rather than a broad-brush one
.
Upvote
0
A different perspective is how Access is regarded as an unwanted child by most in-company Tech Support groups.
My personal belief is this is because:
1) It has the potential to allow relatively unskilled (access/vba) users to directly access production databases (and potentially directly alter or damage them)
2) When you do encounter a skilled user, there's a tendency for them to write applications and then move onto a new job, and leaving unknown Desktop Support or even SysAdmin to try to figure out what it did and fix it when it breaks.
3) As it's really "baby MSSQL" it's beneath the notice of the DBA's that most likely have the skillset to really use it...but it's not robust enough to distribute even as a client to more than a handful of users.
-
With that written, I *love* MSAccess. I also love the "deer in headlights" look that I get from people when I try to explain what the heck I did today.
But, about your original question. If you don't have more than 65K records, and you only want to make a single table, Access would be like using the company jet to head to the local Mall to go shopping. If, on the other hand, you can normalize the data and run queries based on queries, you might see significant performance gains working with your data.
Mike
My personal belief is this is because:
1) It has the potential to allow relatively unskilled (access/vba) users to directly access production databases (and potentially directly alter or damage them)
2) When you do encounter a skilled user, there's a tendency for them to write applications and then move onto a new job, and leaving unknown Desktop Support or even SysAdmin to try to figure out what it did and fix it when it breaks.
3) As it's really "baby MSSQL" it's beneath the notice of the DBA's that most likely have the skillset to really use it...but it's not robust enough to distribute even as a client to more than a handful of users.
-
With that written, I *love* MSAccess. I also love the "deer in headlights" look that I get from people when I try to explain what the heck I did today.
But, about your original question. If you don't have more than 65K records, and you only want to make a single table, Access would be like using the company jet to head to the local Mall to go shopping. If, on the other hand, you can normalize the data and run queries based on queries, you might see significant performance gains working with your data.
Mike
Upvote
0
