Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!ns-mx!umaxc.weeg.uiowa.edu
From: byock@umaxc.weeg.uiowa.edu (Bill Yock)
Newsgroups: comp.databases
Subject: Re: Paradox3.0 'Query can't continue, out of disk space' prob
Message-ID: <5917@ns-mx.uiowa.edu>
Date: 6 May 91 17:07:44 GMT
References: <1991May3.192909.25209@cs.umn.edu>
Sender: news@ns-mx.uiowa.edu
Distribution: usa
Lines: 22

From article <1991May3.192909.25209@cs.umn.edu>, by pazandak@umn-cs.cs.umn.edu (Paul Pazandak):
> I got this message on an AT or 286 with 640k, and 55k memleft.  The
> machine is the server (too) on an Lantastic Net.
> 
> Anyway, I have 23 MB free, and the tables are about 3 MB each - although I trimmed one
> down to 1MB and the other to 800k, and still the same problem!
> 
> I assume that RAM is actually the culprit????  Any thoughts anyone?
> 
> Thanks.

This is a symptom of a corrupted database.  Try running the Tutility program
that comes with Paradox to rebuild the tables.  As a general rule of thumb 
you need to have 2 to 3 times as much free disk space as your largest table.
This increases however, if you are joining several large tables in a query.  On
a network double check where the private directory is pointing to.  You can 
use the Tools Net Setprivate to check.  In some cases this may be pointing to 
a logical disk drive on a network that does not have as much allocated disk
space as assumed.
--
Bill Yock, Weeg Computing Center, University of Iowa, Iowa City, Iowa 52242
byock@umaxc.weeg.uiowa.edu