Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!magnus.ircc.ohio-state.edu!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!uunet!fernwood!portal!cup.portal.com!FelineGrace
From: FelineGrace@cup.portal.com (Dana B Bourgeois)
Newsgroups: comp.databases
Subject: Re: Clipper 5.0 - what's the downside
Message-ID: <39091@cup.portal.com>
Date: 10 Feb 91 07:21:49 GMT
References: <21611@hydra.gatech.EDU>
Distribution: usa
Organization: The Portal System (TM)
Lines: 18

I was told by a tech support person (sorry, I didn't get the name or
bug number - I didn't know it was important to do so) that the current
version might not work properly over non-netware networks.  The tech.
said they are working on a bug-fix which would be available in a few
weeks.  That was two weeks ago.  He suggested I experiment on my network
using the networking example program Nantucket supplies with Clipper 5.0
to see if locking a remote *.dbf file returns a network error or not.
On some networks apparently the error is the only result of trying to
lock a file or record.  I haven't tried this test yet because our 
network is still in the planning stages.  I would love to hear from
someone who uses Clipper (either summer-87 or 5.0) over an Ethernet
using TCP/IP and PC-NFS.  Or for that matter, over any network even
a novelle one.

That's the only negative comment I know about Clipper that might not
be widely known.

Dana Bourgeois @ cup.portal.com