Upsizing, Webifying, Redesigning, or?

[tcb]

An Access database is distributed to 13 geographic regions. The front
and back are split but populated individually by the 13 regions. At
the end of the year the backends are collected and data is all
combined. It's a fairly laborious task.

A few solutions have been suggested:

1. Create a web application using asp.net, sql server, and reporting
services.

2. Create a distributed application with dot net and a common sql
server backend.

3. Stay with Access but have a common back end and use Citrix server.

My client is willing to have me trained in whatever technology it
takes.

The users are currently happy with the Access front end. There is much
functionality with lots of combo boxes, list boxes, sub forms, popup
dialogs, methods of searching, and excellent reporting. Entering data
is a snap. Any suggestions on which method to go with?

I have experience creating ASPs, but can't imagine how I could create a
program with the kind of response and functionality the users are
accustomed to.

Even if we stick with Access we would need to redesign because the
original backend was not completely normalized, and because of new
demands.

 

[Larry Linson]

Interesting.

# 3 -- Using a VPN with Microsoft Terminal Services (and or Citrix) might
require the least modification (e.g., you might have to add some
identification of the region) but will require each location be attached to
the network and the network be up and running for any work to be performed*.

# 4 (not on your list) -- Seems to me, if the database is reasonably
well-designed (e.g., doesn't have 13 different sets of the same AutoNumbers
being assigned and used), that it ought not be awfully difficult to merge
the data. On the other hand, Still, I'd guess that revising the design to
allow this would be the least expensive modification you could make, and
unlike the options you list, wouldn't require that each location be attached
to the network and the network be up and running, for any work to be
performed).

#1 and #2 have essentially the same benefits and drawbacks... there will be
a significant (repeat, significant) learning curve to become proficient in
the DotNet technologies -- not so much so the programming languages, but the
DotNet framework itself. There may be some implementation differences, but
you still have to learn DotNet, you will still have to have someone versed
in SQL Server (or other server DB) as a Database Administrator (at least
part-time) and you have to be attached to a working network* for any work to
be done.

* Internet/intranet

That said, from your personal point of view, having the DotNet knowledge and
experience would be a valuable asset for your future. It's just more
investment than I'd be willing to ask any of my clients to make in me.

I saw something similar happen with a contractor I worked for, and another
subcontractor. No fault of either of them, but the contractor's main client
disappeared due to a corporate merger just as the subcontractor reached
"expert" proficiency and he wasn't able to replace that business (I guess,
better at technical things than at marketing), so shut down his company.
The subcontractor benefitted enormously but paying for his training and
practice were factors in the contractor not being able to stay open long
enough to get enough customers to continue.

 

[tcb]

Thanks for the food for thought. A couple months ago this client had
an outside IT expert consultant company come in to examine all of their
IT practices. The consultant suggested recreating this application
with asp.net, sql server, and reporting services (handily this
consultant also develops programs, however the client has never seen
any program they have developed).

The client wants me to be their developer though, no matter what course
they take. They like me, they're comfortable with me, I know their
program, (and they have more confidence in me than I have in myself).

I have suggested the alternative routes. I always ask myself what
would I do if I was them? I think your suggestion number 4 would be
the route to go (the database does need to be redesigned, however).
The political flow is that they will stick with the IT expert
consultant's advice, and they do have the resources to do that.

If they are willing, and if I decide to accept the proposition, it is
an opportunity for me as you mentioned.

In the end though, what do you think of my concern, would I be able to
create a program with the kind of response, functionality, and
reporting the users are accustomed to?