L
Legacy 277976
Guest
Just throwing this out there if anyone has any good recommendations - at my work, we have (what I imagine is a problem at any number of small to large companies) a lot of exclusive
databases and spreadsheets that had great, ambitious intentions, that just don't talk to one another. As you may know, this never really lasts long because these spreadsheets have to be manually updated. In a span of a couple of months, the information becomes not only useless, but volatile as it is no longer applicable and may convey the wrong messages to people that have moved on.
This is often rooted in the fact the software/spreadsheet/database is excellent at the time but it only lasts as long as the originator stays with the company because either they had supreme authority of their "baby" or the software was never beta tested and made sense to the individual or the department that uses it the most. In the end, the software/spreadsheet/database goes to the grave because no one really appreciates it and some ambitious, maverick Project Manager comes along with the "great unifier" of a database...and History repeats itself.
So back to the automation part - we DO have a central database in our HR department - I want to harness the collective ability to keep that database current and transmit that power to other local, and smallerspreadsheets. One common factor is there is a name, employee ID that can be tied to it.
Is there such a thing that exists to tie these sorts of systems together? Something that can be done with Access? Can be done with Visio?
Sorry, I am blindly asking these questions because I have not yet tackled something like this that was this big - but I know there's a solution out there!
databases and spreadsheets that had great, ambitious intentions, that just don't talk to one another. As you may know, this never really lasts long because these spreadsheets have to be manually updated. In a span of a couple of months, the information becomes not only useless, but volatile as it is no longer applicable and may convey the wrong messages to people that have moved on.
This is often rooted in the fact the software/spreadsheet/database is excellent at the time but it only lasts as long as the originator stays with the company because either they had supreme authority of their "baby" or the software was never beta tested and made sense to the individual or the department that uses it the most. In the end, the software/spreadsheet/database goes to the grave because no one really appreciates it and some ambitious, maverick Project Manager comes along with the "great unifier" of a database...and History repeats itself.
So back to the automation part - we DO have a central database in our HR department - I want to harness the collective ability to keep that database current and transmit that power to other local, and smallerspreadsheets. One common factor is there is a name, employee ID that can be tied to it.
Is there such a thing that exists to tie these sorts of systems together? Something that can be done with Access? Can be done with Visio?
Sorry, I am blindly asking these questions because I have not yet tackled something like this that was this big - but I know there's a solution out there!
