Myles Wakeham wrote:

> For example, let's say that I have 20 customers running the following:
>
> 10 run v1.0
> 5 run v1.1
> 5 run v1.2
>
> I want to release v2.0 of the 'system' (database and application). The
> installer or utility for v2.0 will not be guaranteed what version the client
> was using and what to upgrade from. How is this typically handled?

Professionally :)

All my Version 8 systems have the same database structure. Version 9 has
some Table changes, version 10 has some heavy updates. The master blanks
are available for each, with scripts to populate the security database,
and initial site setting ( which can be adjusted before running ).

There is are scripts to upload 8to9, 8to10 and 9to10.

There are a few changes to triggers and procedures during the life of a
version, but that is not allowed to affect the raw data, and so does not
become involved when moving between versions.

I'm lucky that the data content is fairly stable, but even adding stuff
this process should work. But it does help to know what IS running on a
site ;)

--
Lester Caine
-----------------------------
L.S.Caine Electronic Services