I spend a fair amount of time handling problems that occur when the words "spreadsheet" and "database" are considered synonyms. Spreadsheets might be good for small ad-hoc data storage and analysis, but they're awful for the volumes and complexity of data we try to manage with them.
We have critical financial and project management information passed around by email in spreadsheets as if that is just how things should be. We could (and in my opinion should) be using proper databases with data type and format rules that help to keep the data clean. The reason we do not do so is that the step into a spreadsheet is very small, but the step from spreadsheet to database is huge. Everyone knows how to use a spreadsheet and the tools to do so are readily available in the office. The freedom they afford, however, comes at the price of accuracy.
Mokalus of Borg
PS - I can't see a way to make databases as easy as spreadsheets.
PPS - Microsoft Access tries, though.
4 comments:
I've recently tried to make the jump from Excel to Access, but have to admit that the step is quite a large one.
Even with Microsoft's usual help mechanisms and the inherent formatting standard across the Office platform, I have still found it difficult to grasp the entire concept.
I believe that part of this is due to the language employed. Most of the terms of reference within the world of databases are used quite frequently in other ways through out the regular world. This apparent contrast in definition only adds to the complexity of the issue, and as a result tends to put a person off. This is especially the case with new users, who more often than not throw their arms up in despair thinking if IT&T are so wizz bang, they can fix it!
That's just it. It's really hard to make databases easy and accessible to the general public. A similar problem exists with programming, though many have tried (and there's some pretty cool research in that area, too).
I didn't understand databases at first, and thoroughly disliked my university courses on the subject. After working with them daily for five years now, I get it. For those with only a casual relationship to databases, the situation is much more difficult.
Probably a part of the problem is that most people think of their data as having no structure at all, and databases are all about structure.
What's really interesting is I spend a fair amount of time using databases for reporting through the program "Business Objects", however even with my knowledge of this program, and the necessity of information accuracy and order, I am unable to convert this knowledge into a practical use when trying to design a basic database through Access.
Clearly there's a difference between using software and designing it, just like there's a difference between driving a car and building one. I have no idea how to build a car.
Post a Comment