🚀 go-pugleaf

In article <1991Jan21.135925.129@biivax.dp.beckman.com> rlmeyering@biivax.dp.beckman.com writes:
>
>Since my initial request for Help I have been told by 3com that the .exe file
>is overlayed across the Net (this sounds right). I have also been told by
>3com that clipper is a poor performer on 3com when the number of nodes on
>the Net is above 6. 3com also stated that clipper downloads the indexes
>to the workstation for all database queries. 3com recommended using Gupta
>SQL server and replacing all of the database access commands with Planet
>software's library for Clipper SQL server access commands. 3com could offer 
>no feeling for the improvement I would gain from these changes.
>
>The workstations have 1mb of memory each. Also, we had several "out of memory"
>errors prior to using the BLINKER linker.
>
Hi... I don't have an immediate answer for you but switching to Gupta SQL
seems a little extreme.  As you pointed out the conversion should be
easier with Clipper 5.0 when the RDDs are released.  Using them in the
"simplest" mode would require virtually no program modifications.

I have worked with a programmer at GTE using Clipper and they have a 3Com
network and there was never a complaint with the speed... they even had a
number of users logging on remotely through a modem (maybe the delay was
absorbed in that case).

I don't imagine I'm being a lot of help here but will suggest that there
might be a 3Com situation (environment problem or something) that isn't
optimal.  It isn't something like a ton of files in the subdirectory or
anything is it ?

tom   tleylan@pegasus.com
ex-senior systems analyst / Nantucket Corporation