Re: VARPG (was Design Change Requests)

[Booth Martin <booth@xxxxxxxxxxxx>]

Oh.  Then it is a design issue.

VARPG uses a runtime environment.  If you try to use that model then, 
yes, updates would be tiresome.

However the runtime is only about 15 megs.  Building it into the 
application locks the two together, and updates are no longer an issue. 
 I stored the application (including runtime) on a server.  When a user 
opens the desktop version, the desktop version checks to see if its 
still King.  If not, it replaces itself with the newer version. 
Downloading 20 megs once in a while from a server is not much of a 
burden imho.

Still, the fact remains, VARPG can't gain traction.


rob@xxxxxxxxx wrote:
> I do see it as an issue different from the bulk of your windows 
> applications.  For example, how often do you update MSWord - once a year?
> How often do you update a program for your ERP (or other iSeries stuff for 
> other types of midrange-l-ers) - four times a week or more?
> I have a hard enough time personally checking for Windows updates once a 
> week.  Now imagine having your users checking for VARPG updates daily, or 
> more, at the same time.
>
> Rob Berendt