Page 1 of 1
DBF file explodes with blank records
Posted: Thu Sep 11, 2014 4:24 am
by bobvolz
I recently had a problem with a dbf file that exploded from 200000 records to a size so big it could not be opened by xbase. It appears all the records added were blank.
I use foxcdx. The file has no memo field. It was a simple dc_addrec() call. There is no loop in my function that would have caused it to just keep adding records.
Has anyone ever experienced anything like this?
I believe the user that this happened to was running Terminal Server on a new WIN 2008 64 bit server.
I was able to restore from backup but this was pretty scary.
Any insight would be appreciated.
Bob Volz
Re: DBF file explodes with blank records
Posted: Thu Sep 11, 2014 7:02 am
by rdonnay
Bob -
That is very strange.
Was it exactly 200,000 blank records?
Roger
Re: DBF file explodes with blank records
Posted: Thu Sep 11, 2014 7:37 am
by bobvolz
Hi Roger;
I was speaking in approximate terms. The file had a little over 200000 records which was fine. It's a big file. But the system went wild and expanded to a size xbase could not read. Bobby Drakos was covering for me while I was in Europe and he thought it looked like the file was filled with blanks. It grew to 34GB.
I was just wondering if anyone else ever saw this happen.
Re: DBF file explodes with blank records
Posted: Thu Sep 11, 2014 8:02 am
by rdonnay
In all my years of Clipper and Xbase++ development, I have never seen this.
Re: DBF file explodes with blank records
Posted: Thu Sep 11, 2014 9:06 am
by Wolfgang Ciriack
To me this happend two times at two different customers, but only to 2,xx GB and the dbf could not opened anymore.
Re: DBF file explodes with blank records
Posted: Thu Sep 11, 2014 9:32 am
by bobvolz
Leave it to me to be the first. But it looks like it happened to Wolfgang as well.
Wolfgang. What OS wee you using at the time? and how do you add records?
Bob Volz
Re: DBF file explodes with blank records
Posted: Thu Sep 11, 2014 10:13 pm
by Wolfgang Ciriack
Hi Bob,
i do not think, that this is a OS specific problem, one happened with WinXP (1,5 years ago) one happened with Win7 64-bit (0,5 years ago).
Both happened to a dbf file located in a network. I add records with a function, that tries to lock the record for some time and return .T./.F.