I maintain a fairly elaborate set of .dbf tables representing images of
tables in an Informix engine on a Sun server. My images are created and
maintained on a Windows 2k server on a daily (overnight) basis.
I create the .dbf with a program of my own which reads a text file from
the Informix server and builds a .dbf on the windows side. It is
essentially 'append from' and very fast.
There are 100 or so of these .dbf tables created every morning (M..F)
and some of them get larger on a daily basis.
There is some preprocessing of these tables by Clipper apps I have
written. One day last month one of the Clipper apps failed. It had run
flawlessly five days a week for five years. Now it fails..
A little troubleshooting suggested it failed while attempting to index
the principal .dbf table. I noted that the table size was approaching 2
Gigabytes. Clipper didn't seem to have any problem with the size of the
table so I determined to 'cook' it down some before indexing it.
I got the file size down to 900 Megabytes or so and indexing it went
smoothly. Problem solved.
Maybe not. During the day we use Visual FoxPro 6.0 to do various
interesting things using my .dbf images. Yesterday, Feb 28, VFP6.0
attempted to open my 2GB table, barfed and declared "Not a table".
Clipper thinks it's a table but can't index it.
Underlying filesystem is NTFS. Is there a known way through or around
this 2GB file limit?
--
Joe Wright
"Everything should be made as simple as possible, but not simpler."
--- Albert Einstein ---
