Susan Harkins
harkins at iglou.com
Mon Jul 7 11:53:44 CDT 2003
John, could you provide a rough estimate of the number of support calls you've received on applications you didn't build? How about the amount of time required to get these applications up and running? How many couldn't you fix either because the db just wasn't fixable? Can you relate this time to $'s and if so, can you also provide a realistic estimate to how much time you spend supporting/fixing applications your department develops -- as a comparison? Don't include maintenance and updates, etc -- that'll just confuse them -- but you need to show how much the current arrangement costs the company in unnecessary support, debugging and fixing -- not to mention the employee time spent doing a task that's outside his or her job description. I think some easy charts that accent time spent repairing, supporting, etc. would go a long way toward showing inefficiency. Susan H. > > The reason that I am writing to the list, is that I want ammo for my > hearing tomorrow. It is just an initial hearing, but I would like to > make some solid impressions. To do this I want facts, or at least > quality in my statements. As you all know, Access is unique in that it > can be used by a novice office worker for simple desktop dbs, as well as > hard core programmers pumping out intense programs, and everything in > between. But where do you draw the line? I have said that if someone > creates something for their own use, that is saved to their HDD (i.e. a > tool for them to do their job), then I don't have a problem with it. > However, if it becomes, or is to become, a tool that they whole > department will become dependant on, and/or it is going to reside on the > network, then it should be created and managed by the MIS department.