[AccessD] OT - My union grievance

Just as a note, when I worked for the Tech dept at the NY Attorney General's
Office, the policy was, if we don't create it, we don't maintain it.  The
reason being that there was more than enough work to handle taking care of
systems that were created by the dept, and that with so many users, it would
get out of hand to take care of everyone's "little database", which were
usually non-normalize and in some case unrelated.

Nancy L.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Susan Harkins
Sent: Monday, July 07, 2003 12:54 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] OT - My union grievance


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.


_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com