[AccessD] Article on upgrading

First, why bother with the upgrade? Two potential answers:
1, Because the DB size limit is going to be a problem. In many cases this is
not an issue, but my philosophy is, Plan For Success, according to which
maxim what you originally thought were going to be 1K users turns out to be
1M users.
2, Deploy the initial virgin in MDB or AAcdb format, and hope that it works
for the short-term.
3. Be prepared to go to SQL Server if you should be so lucky as to achieve
success. (Fuller's fifth law: only successful apps require upgrades; the
rest die on the vine).

And these numbers remind me of the old joke: How many kinds of programmers
are there? Three: those who can count and those who can't.

A.

On Thu, Jul 28, 2011 at 2:13 PM, Susan Harkins <ssharkins at gmail.com> wrote:

> This is good advice for actually performing an upgrade, but I'm looking for
> questions you might ask when deciding whether you actually should or want to
> upgrade -- see the difference? What kind of questions do you ask your
> clients before you actually get there -- what kinds of questions do they ask
> you when they begin to think about upgrading?
>
> Thanks Arthur! Please feel free to play again! ;)
> Susan H.
>
>