My boss stole my database!

Happens all the time

Hello

Its life i am affraid i have created many databases for my company. I made on which would of saved them £16000 a year in man hours and it was a simple database to stop our operation team spending 4 hours a day creating reports with the DB it took 30 seconds to generate 15 reports. They decided not to use as IT would not support it and if i left and it broke it would be useless, most companies don't support IT solutions created by employees. Don't take it personnally i would learn from it and then improve it and then sell yourself.

Any how the web is the way forward easy to deploy and a bigger market, i only create access database for the people who are not clued up with the web.
 
most companies don't support IT solutions created by employees

this is something that really varies from company to company

of the places i've worked

1) US communication infrastructure company: you build it, you maintain it. IT doesn't do Access or Excel. Lots of databases, some written by external management consultants

2) UK food retailer: you build it, you maintain it. It doesn't do Access or Excel. IT hate Access, but will give you tips on T-SQL, SQL server, OLAP, MDX, just to get users off their backs and onto yours

3) US bank: you build spreadsheets or Access, you run it and support it. you can ask IT about it, there is a team for Access/Excel but they will take a month and rewrite what you've done. historically there is one large Access database that IT support, but nobody else can develop on it (so we all cloned it)

4) swiss investment bank: there is a specific team that supports Access databases. the ones they support is fairly stable, if you build a new database, you have to go with your begging bowl to get it supported

5) UK retail/investment bank: i work in the team that specifically supports Access databases, we write from requests from all over the business. if you've written it, you come with your begging bowl to ask us to support it. IT forward any Access questions onto us
 
Its galling to think your bosses are making fortunes out of your expertise (but i expect chemists working for drug companies feel much the same)

However, a lot of the time solutions developed for one situation are not directly marketable anyway, and there are no fortunes there.

its one thing designing a system that is (relatively) unsecured, where the developer is on site to fix issues, and provide support, and the system is tailored for a specific company/industry solution.

You try changing this to be a general marketable off the shelf solution.

Among other things, you need robust security, user login/functionality control, on line help files, provision for remote support, better run time support, and the app will probably needs a lot of attention to add functionality that your company doesnt need, but others may well.
 

Users who are viewing this thread

Back
Top Bottom