Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uunet!viusys!uxui!unislc!thayne
From: thayne@unislc.uucp (Thayne Forbes)
Newsgroups: comp.databases
Subject: Re: some questions on DBASE III +
Message-ID: <1991Mar15.162050.16222@unislc.uucp>
Date: 15 Mar 91 16:20:50 GMT
References: <68396@brunix.UUCP>
Organization: unisys
Lines: 23

From article <68396@brunix.UUCP>, by pew@cs.brown.edu (Peter E. Wagner):
> In article <1991Mar13.101820.4102@pegasus.com>, tleylan@pegasus.com (Tom Leylan) writes:
> |> In article <20990@shlump.nac.dec.com> yychow@pasm07.enet.dec.com (yychow) writes:
> |> 
> |> Right off the bat you should avoid expressly using any particular workarea
> |> and simply use the SELECT 0 construct.  This will open the file in the next
> |> available workarea.  You should refer to workareas by their alias names
> |> after you have opened a file there.
> 
> I don't think that dBase III+ supports SELECT 0.  It's been a while,
> though.
> 
What he said.  I had the same problem when I had to port to an old version
of Foxbase the was stricly compatible. I wrote a procedure called
SELECT0 that did the same thing.  I don't remember it all now but I did
a while loop, counting from 1 to 10, and did a dbf() for each area to
see if a file was open.  It would return on the first empty area.

Now does anyone remember if dBase had the dbf() function?
-- 

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
# The opinions expressed above are my wife's, but she said I could use them.