Path: utzoo!utgpu!watserv1!watmath!mks.com!tslwat!louk
From: louk@tslwat.UUCP (Lou Kates)
Newsgroups: comp.databases
Subject: Re: Opinions wanted on Empress Database Package and 4GL
Message-ID: <332@tslwat.UUCP>
Date: 10 Oct 90 04:02:08 GMT
References: <1990Sep26.192938.1101@tropix.uucp> <96@thinc.UUCP> <270DDFD3.426A@telly.on.ca> <330@tslwat.UUCP> <27112761.EC@telly.on.ca>
Reply-To: louk@tslwat.UUCP (Lou Kates)
Organization: Teleride Sage, Ltd., Waterloo
Lines: 28

In article <27112761.EC@telly.on.ca# you write:
->In article <330@tslwat.UUCP> louk@tslwat.UUCP (Lou Kates) writes:
->>In article <270DDFD3.426A@telly.on.ca> evan@telly.on.ca (Evan Leibovitch) writes:
->
->>and  its   often handy to have the  development
->>system on the client's machine.
->
->This, I guess, is a matter of philosophy. Having development systems on
->each clients' system allow, even encourages, "quick fixes" which are not
->applied globally. The developer is saddled with the support nightmare of
->dealing with different clients, each of whom uses a version of the
->software on their system slightly different from the original.
->
->And I don't know about you, there are clients I have who I want nowhere
->near the ability to change the database schema/dictionary.
->

The reason   that  having the   development system on the  client
machine is useful is:

(1)  the client  base has  a wider   variety of machines than you
     have inhouse

(2)  clients would not typically wish  to make schema changes but
     they might   want  to interactively  perform ad hoc  queries
     using SQL and possibly write up some reports themselves

Lou Kates, Teleride Sage Ltd., tslwat!louk@watmath.waterloo.edu