To All You IT/MIS Genius'....
Perhaps you can shed some light on this issue.
I am a self taught Access programmer. However just a technical user on this forum, over the last few years I have designed, developed, written, and implemented some pretty sophisticated and useful Access databases for the companies that I've worked for. For example, the last company I worked at I developed a database (with the help of many members of this forum, as well as the several books on Access that I have read) that handled and tracked all their customer complaints, customer returns, corrective action system, document control system, human resource training system and Q.C. tracking. This can be and was done in MS Access and the program had virtually NO BUGS. I had designed very professional looking menus and GUI. The problem that I had at that company was 1. ~ It wasn't in my job title or postion description to do this... however I saw the need and willingly did the work on mostly my own time. 2. The IT/MIS people for some reason seemed miffed by the functionality and utilization of this program. Actually they seemed quite upset about the fact that I had done this and implemented this program, although I informed them from the beginning and invited them to participate in the design and development.
Of course they didn't show an interest in being involved.
Well recently I've left that company and have joined another company that has the same needs... for a comprehensive database (right now they are using Excel for everything). I've proposed writing a similar database as I did at my last company and volunteered to do the brunt of the work. But I've been met with a great deal of resistance from the IT department. Basically they say they do not support Access databases and their reasoning is that they would rather do it in SQL (except without a kick in the pants... it would never get done) So I say to these guys... here is the requirements for this database.. and I give them the tablenames, the field names, the query information, the relationships... etc. and of course their response is well we will have to evaluate the need and then get back to you. The funny part is... in the time they need to evaluate the need and to finally come back with a solution, I could have had the Access database designed, written, implemented, debugged, and rolled out for full implementation and utilization. I sometimes get the feeling that the IT/MIS guys have some kind of Access Phobia. Can someone shed some light on this for me?
Thanks,
Tp
Perhaps you can shed some light on this issue.
I am a self taught Access programmer. However just a technical user on this forum, over the last few years I have designed, developed, written, and implemented some pretty sophisticated and useful Access databases for the companies that I've worked for. For example, the last company I worked at I developed a database (with the help of many members of this forum, as well as the several books on Access that I have read) that handled and tracked all their customer complaints, customer returns, corrective action system, document control system, human resource training system and Q.C. tracking. This can be and was done in MS Access and the program had virtually NO BUGS. I had designed very professional looking menus and GUI. The problem that I had at that company was 1. ~ It wasn't in my job title or postion description to do this... however I saw the need and willingly did the work on mostly my own time. 2. The IT/MIS people for some reason seemed miffed by the functionality and utilization of this program. Actually they seemed quite upset about the fact that I had done this and implemented this program, although I informed them from the beginning and invited them to participate in the design and development.
Of course they didn't show an interest in being involved.
Well recently I've left that company and have joined another company that has the same needs... for a comprehensive database (right now they are using Excel for everything). I've proposed writing a similar database as I did at my last company and volunteered to do the brunt of the work. But I've been met with a great deal of resistance from the IT department. Basically they say they do not support Access databases and their reasoning is that they would rather do it in SQL (except without a kick in the pants... it would never get done) So I say to these guys... here is the requirements for this database.. and I give them the tablenames, the field names, the query information, the relationships... etc. and of course their response is well we will have to evaluate the need and then get back to you. The funny part is... in the time they need to evaluate the need and to finally come back with a solution, I could have had the Access database designed, written, implemented, debugged, and rolled out for full implementation and utilization. I sometimes get the feeling that the IT/MIS guys have some kind of Access Phobia. Can someone shed some light on this for me?
Thanks,
Tp