[AccessD] Poll - What Access version

Arthur Fuller fuller.artful at gmail.com
Thu Sep 17 13:04:33 CDT 2020


Hi JWC,
I consider myself semi-retired; ias Michael Corleone said, "I keep trying
to get out, but they keep dragging me back in." Most of the Access  apps I
wrote required a complete understanding of the particular business or
governmental niche. For example, one app I wrote (for a travel-event
company, i.e. given a tour by U2, they would buy 400 tickets to each stop
on the entire, then package these with flight pans and hotel bookings and
even travel from airport to hotel to concert and back, and the return
flight -- all done with a click. The email reply would list your itinerary
in chronological order, al steps arranged by date and time. Initially, I
came on board to solve a small problem, but as I accumulated an
understanding of the business, I suggested improvements. For example, why
not pipe all this data into an entry into an accounting system they
currently use?
 Add to this business model four different branches loosely defined by
time-zone; combine this with the limited-inventory problem. Eventually this
grew into an enterprise system. Should I retire or be run over by a bus, it
would take a long time to educate a new programmer, no matter how gifted,
to take over. Therefore about 30% of my time was devoted to documenting the
system and the business, so that an incoming developer could read those
hundred pages at least twice, and eventually come to an understanding of
the model.
To be sure, I made lots of mistakes, the largest one involving what began
as a local app and then required migration to SQL Server and Terminal
Services, so that everyone in the four offices (each in a different time
zone) knew exactly how many seats were left for any given concert. Add to
this, "Do you want to fly first class? Ditto for hotel accomodation, etc.
Each successful step exposed new problems to solve. This was most certainly
not a top-down problem, nor a bottom-up problem. I can't think of an
acronym for it, but the essential idea is this: 1. Begin with a small
problem.
2. Solve it.
3. The solution presents new opportunities, i.e. new problems.
Repeat.

I have some other examples, but I'm sure that you do too. So let's hear
about them.

On Thu, Sep 17, 2020 at 12:43 PM John Colby <jwcolby at gmail.com> wrote:

> 1) What access version(s) do you develop new in?
>
> 2) What Access versions do you maintain databases in
>
> --
> John W. Colby
> Colby Consulting
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


-- 
Arthur


More information about the AccessD mailing list