when to use a database

[teiben]

I searched help, but didn't find any answer. Is there some set of rules or guidelines about when to use a database? (when to use a spreadsheet). My boss wants me to do this project, matrix, which I think should be done in Excel.

 

[Parker]

I searched help, but didn't find any answer. Is there some set of rules or guidelines about when to use a database? (when to use a spreadsheet). My boss wants me to do this project, matrix, which I think should be done in Excel.

More detail might be nice

 

[dcx693]

Yes, more detail would be nice. For small datasets, I feel it's a matter of whether or not the person doing the work really understands how to design a database....because if you don't know how to get data out of a database, then it's really dangerous. And if you're asking whether a spreadsheet or a relational database manager would be better, chances are you're better off doing it in the spreadsheet. Unless you're willing to take the time required to learn how to use the RDBMS correctly (which I do encourage) the tools in Excel, for example, are usually adequate for "light" database needs.

I get so many questions from spreadsheets users on (1) why empty cells are considered this mysterious Null thing by Access, (2) why doing a vlookup is so difficult, (3) why they can't just copy and paste an entry into an entire table "column", (4) why they can't just edit a calculation in one table "cell" while leaving the other "cells" alone, (5) why they can't do a sum acrosss a row of data in their table, (6) why they can't insert a row into a table (7) why they can't change an autonumber by typing over it, etc.... Basically, they want Access to act like a spreadsheet.

 

[teiben]

What I was looking for is an already established set of rules that may exist. I've designed a few databases, and often I ask myself is it really necessary