D
David F. Cox
I do some work for an small, but growing, international organisation on a
vouluntary basis because I believe it helps a lot of people enjoy life
better. I want it to prosper.
It is using an Access Database being developed by a buddy of the Chief Exec
which I regard as woefully badly designed, implemented and tested. I believe
that the task they need it to do probably requires an upgrade to SQL Server
in the near future.The developer is a nice guy, a has worked really hard,
and I wish him no ill. If he would agree to some training, counselling and
supervision and do the job right I would be happy.
Firstly I need to convince the Boss that he has a problem.
Secondly I need to persuade that the money spent on doing it right is a
necessary investment,
Thirdly I need good advice about how to find a compentent developer/tutor
for the job.
I do not expect treatises on this newsgroup, relevant links would be
appreciated. I can do the "collect and collate" work and pass it on.
Some of the problems I see:
The application is a membership database. Members lose cards, and get new
cards and numbers, so a member may have multiple membership numbers. Numbers
are manually entered.
Nevertheless the key is the membership number.
Except for the few members that have had their numbers wiped because some
"membership numbers" are used for classes of membership.
And arbitary negative membership numbers are used for "prospective members".
And some invented membership numbers are used. Nobody knows all the reasons
for that.
If a member gets a new card then all of the attendance records with the old
number have their old key overwritten with the new one.
Keyboard shortcuts do not work, Data entry is all textual, but requires a
mouse.
Few null fields. If something is not known the data entry clerk has to enter
"UNKNOWN", ot "UNKOWN", if they follow some the instructions.
Am I right? Do we really, really need an MVP?
David F. Cox
vouluntary basis because I believe it helps a lot of people enjoy life
better. I want it to prosper.
It is using an Access Database being developed by a buddy of the Chief Exec
which I regard as woefully badly designed, implemented and tested. I believe
that the task they need it to do probably requires an upgrade to SQL Server
in the near future.The developer is a nice guy, a has worked really hard,
and I wish him no ill. If he would agree to some training, counselling and
supervision and do the job right I would be happy.
Firstly I need to convince the Boss that he has a problem.
Secondly I need to persuade that the money spent on doing it right is a
necessary investment,
Thirdly I need good advice about how to find a compentent developer/tutor
for the job.
I do not expect treatises on this newsgroup, relevant links would be
appreciated. I can do the "collect and collate" work and pass it on.
Some of the problems I see:
The application is a membership database. Members lose cards, and get new
cards and numbers, so a member may have multiple membership numbers. Numbers
are manually entered.
Nevertheless the key is the membership number.
Except for the few members that have had their numbers wiped because some
"membership numbers" are used for classes of membership.
And arbitary negative membership numbers are used for "prospective members".
And some invented membership numbers are used. Nobody knows all the reasons
for that.
If a member gets a new card then all of the attendance records with the old
number have their old key overwritten with the new one.
Keyboard shortcuts do not work, Data entry is all textual, but requires a
mouse.
Few null fields. If something is not known the data entry clerk has to enter
"UNKNOWN", ot "UNKOWN", if they follow some the instructions.
Am I right? Do we really, really need an MVP?
David F. Cox