dBase IV, Netware, and file already open
Tim Mills-Groninger
3.11 network.
MDXs are shown as corrupt, and when you try to reindex, it gives an error
message along the lines of "File already open" or "File in use." Sometime
there's a "Disk Full" error when appending to a table--even thouhg there's
significant disk space left.
Files will behave on a local drive. In some cases I've copied the files
locally, reindexed, then copied back to the network.
We're also using dBase IV Runtime for the Mac, and experience the same
problems there.
Any suggestions? Thanks,
tim
Tim Mills-Groninger
Chair, Technology Resource Consortium (TRC) http://www.igc.apc.org/trc/
Associate Executive Director
Information Technology Resource Center (ITRC) http://www.mcs.net/~itrc/
6 N. Michigan Ave, Suite 1405
Chicago, IL 60602
voice: 312/372-4872
fax: 312/372-7962
email: it...@igc.apc.org
Allen Wright
Tim Mills-Groninger wrote:
>
> We're seeing occassional trouble w/ a dBase IV 1.5 app running on a Netware 3.11 network.
>
> MDXs are shown as corrupt, and when you try to reindex, it gives an error message along the lines of "File already open" or "File in use."
I'm seeing a very similar / same problem. My environment is a little
different. I'm running dBase IV 1.1 on a Novell 2.15 server. The
environment has been in place for a number of years and running very
well.
Over time new (faster) user machines have been added to the network. I
first noticed the corruption of MDX files occasionally when using a
486-66 workstation. Recently we installed 4 Pentium 100's and the MDX
corruption began showing up immediately in those machines.
The REINDEX command is met with "File already open" errors so a reindex
cannot be done on those P100 computers. Loggin in from a slower
computer, XT/AT/386 allows the dBase files to be opened and reindexed
without any problems.
Now, does anyone have a solution which allows for the use of fast
machines ? I'm in the process of upgrading the network to Netware 3.12
but according to Tim that isn't a fix.
Help ?
--
Allen Wright FCX Systems, Inc.
mailto://awr...@access.mountain.net 2 Eastgate Plaza
http://www.mountain.net/hp/fcx Morgantown,WV 26505
304 291-3291, fax 291-3299
Romain Strieff
Allen Wright wrote:
>
> Tim Mills-Groninger wrote:
> >
> > We're seeing occassional trouble w/ a dBase IV 1.5 app running on a Netware 3.11 network.
> >
> > MDXs are shown as corrupt, and when you try to reindex, it gives an error message along the lines of "File already open" or "File in use."
>
> I'm seeing a very similar / same problem. My environment is a little
> different. I'm running dBase IV 1.1 on a Novell 2.15 server. The
> environment has been in place for a number of years and running very
> well.
>
> Over time new (faster) user machines have been added to the network. I
> first noticed the corruption of MDX files occasionally when using a
> 486-66 workstation. Recently we installed 4 Pentium 100's and the MDX
> corruption began showing up immediately in those machines.
>
> The REINDEX command is met with "File already open" errors so a reindex
> cannot be done on those P100 computers. Loggin in from a slower
> computer, XT/AT/386 allows the dBase files to be opened and reindexed
> without any problems.
>
> Now, does anyone have a solution which allows for the use of fast
> machines ? I'm in the process of upgrading the network to Netware 3.12
There are 2 problems.
The FAO messages comes from dBaseIV prior to version 1.5 xx71. When
these versions shipped, nobody had even dreamt of machines with more
than 33MHZ. These versions used the internal clock to generate temporary
filenames (2 are required for reindexing) Since your machines are so
fast, the clock has not moved yet, and dBase gets the same name for the
second tempfile generating this error.
Also when using VLM with these old versions you'll get the other errors
FULL/etc. Try to remove SHARE or upgrade to version dBase 5 for DOS.
MIKE WEBB
AW> From: Allen Wright <awr...@access.mountain.net>
AW>
AW> Tim Mills-Groninger wrote:
AW> > We're seeing occassional trouble w/ a dBase IV 1.5 app running on a N
AW> > MDXs are shown as corrupt, and when you try to reindex, it gives an e
AW> sage along the lines of "File already open" or "File in use."
AW>
AW> I'm seeing a very similar / same problem. My environment is a little
AW>
AW> Over time new (faster) user machines have been added to the network. I
AW> first noticed the corruption of MDX files occasionally when using a
AW> 486-66 workstation. Recently we installed 4 Pentium 100's and the MDX
AW> corruption began showing up immediately in those machines.
AW>
AW> The REINDEX command is met with "File already open" errors so a reindex
The best cure is getting a later build of dB4 from Borland, build xx71
of version 1.5 minimum. I'm told it's available from Borland for
a nominal fee for registered users.
There's also a workaround called idxfix.zip, available by anonymous
ftp from ftp://ftp.sckans.edu/pub/dbase/dos/idxfix.zip. It has a .BIN
file you load within dB4 and a TSR you can load before dB4 (take your
pick of which one you wish to use).
Hope this helps!
---
ţ MegaMail 2.10 #1784911682:TRS-80 * The Best 8-bit Computer Ever Built!
PHIL GREENBERG
If you installing build xx71, make sure that you have the serial numbers of t
he original installation (it's on the screen when you bring up dbase) and you h
ave the serial numbers of all of the add-on licenses (when you use adduser4). T
he additional licenses installed are un-installed when you do a multi-user in
stall of build xx71. The build is available from Borland sales for $15 800-336-
6464.
lloyd.w...@gmail.com
IDXFIX.ZIP is available at http://www.oocities.org/geoff_wass/dBASE/GaryWhite/dBASE/dosstuff.htm
Thanks for this guys - 19 years later!
Moved a client's dBASE IV application on netware 3.12 to a Virtual Box on a core i7 with an SSD - suffice to say we came across the same corruption problems and this fixed it/saved the day.