[Closed] Too many spreadsheets - export into database?

I assume these are financials? If you intend to do some data mining and trending then yes. Otherwise, organising them in chronological archives and naming them a bit better might be sufficient.

SQL Server might be better - then write ASP.Net pages to read from / write to it?

how do you mean pile?

are they loads of spreadsheets generated by different people from different sources of information

or are they spreadsheets generated by people from a single source of information.

a database would be good for people to extract info from if they are all using them same data source, just bear throught to whether you want people to be able to edit that source data ( and thus muck up other peoples reports who are exttracting the info for their own uses )

Depends on what is in the spreadsheets - it it's just list based data then upsizing to a database may be the way forward, but to get the benefit you really want to look at breaking it out into some sort of normalized model.

If it's more calculation heavy stuff then uploading to a database will only be part of the solution as you will need some form of front end to provide the same functionality / presentation layer.

depends what you aim to gain from collating them all. Are they compatible with each other for starters?

No, not financials. We have a lot of template spreadsheets which are opened each time a new project is opened, so there's quite a lot of information saved to the same fields in a new spreadsheet each time. As everything is tracked by project ID and, because we generally use templates, normalizing should be fairly straightforward. I implied through the use of commas that it's becoming tedious shifting through so many spreadsheets each time a new project was opened up. I'd be using asp to extract the data (I dabbled in sql and asp many moons ago).