Design issue for table with 150+ colums

[oganos]

Howdy all,
First time poster. I have a question to throw out regarding the layout/setup of info in a spreadsheet that has to track a large number of changes.

The goal of the spreadsheet is to:
- record date that a change was implemented
- record new version number
- record the change that was made
- record when the change was applied to the master image
- record when the change was applied in production (this will sometimes be pushed out at once but sometimes on separate days)

There are approximately 50 sites with around 150 computers total

The problem I'm running into is a design that will easily show all the data in a readable format. Any suggestions or pointers would be greatly appreciated.

Thanks,
Oganos

[roki4]

Are you tracking changes within the spreadsheet itself or are you tracking changes that you are referencing from somewhere in your production process (I assume it's a production process)?

[Spencer101]

Hi,

There are many ways of recording and displaying this type of data, but it VERY much depends on what you're working with. Any chance of some sample data just to see what you have so far?

[Kyle123]

I'd use a database then just run queries depending on what I'd want to see. This becomes trivial in a relational database, you can have as many changes/computers/sites without worrying about layout. Layout is handled by the report

[oganos]

POS Image Change Control.xlsx
Thanks for all the quick responses.
Roki:
Yes I'm tracking changes to our Master image and then when that change is implemented in the production environment for registers at our stores not changes to the spreadsheet.

Spencer:
We don't have much data yet (I just set the control version to 1.0 last week) but I've attached some sample data for what I have.

Kyle:
I would prefer the DB route but I was asked for a spreadsheet so I thought I'd give it a go to see if it was feasible first. Right now it looks a bit unwieldy