🚀 go-pugleaf

From article <1992Oct5.131632.27931@geac.com>, by allen@geac.com (Allen Septon):
> Hi,
> 
> I finally started this newsgroup and have yet to see a posting.
> I guess everyone is afraid to be the first poster.
> 
> Our current customer base is very reluctant to jump into the new
> technology of client/server. We plan to use MS-WINDOWS based frontends
> and initially GUPTA for a database on the backend.
> 
> What experience have people had with reluctant customers and how have
> you handled it.
>
My opinion:  Client/server architectures fit well with the current
mainframe/terminal based applications in place in many IS shops.
It allows one to continue to use the mainframe as a central data
source, possibly by front-ending it with translation tools or 
a second, more modern, database server.  With the widespread use
of Windows and the Mac, client applications have an existing platform
already in place.

Using existing infrastructure is BONUS in todays climate of tight
budgets.  Client/server also affords a phased approach where 
mainframe systems can be phased out over 5-10 year time spans as
intermediate database servers become more functionally complete.

Would I recommend client/server to a customer who has no
existing infrastucture?  Maybe.  Peer-to-peer may be more
flexible but less supported.  

If you educate your customers, I don't see why they would be
reluctant or scared beyond the nervousness associate with
any type of change.

-- 
........................................................................
Steve Anastasi	        "Give a man a fish, and you can feed him for
smanastasi@mmm.com       a day.  Teach him to fish and you can tax him!"
St. Paul, Minnesota                 - hey, I wrote it!