How you store the bits, how you transmit the bits, and how you visualize the bits are three very different things. > Data needs to live in a database - not an

How you store the bits, how you transmit the bits, and how you visualize the bits are three very different things. > Data needs to live in a database - not an Excel file. > Access should be granted for each according to their needs. I mean, for enterprise users it's pretty hard to beat an Excel file in SharePoint. You could model the data, put it in a relational database, and build a simple web app for CRUD operations, but unless you're adding additional business logic, I've noticed a lot of the time you end up with a table view that's not as powerful as a spreadsheet and maybe a form to enter data. I definitely agree that it doesn't make sense to e-mail spreadsheets around, but persistence and user interface are different layers.