Hello everyone!
Records looks deleted in the browse window but in fact they aren't
(and they don't process as if they are.)
If I look at the DBF file (in ASCII), I see that an asterisk/space
(asc. 42 and 32 respectively) is used at the beginning of the records
to represent whether or not they are deleted.
If I look at the faulty records, I see that they have ASCII 26 instead
of ASCII 32.
Does anyone know why this may happen?
If I browse the tables in Visual fox, they don't look deleted like
they do in 2.6a.
I have this problem on some very big tables!
For big I mean approx. 1 Gigabyte DBF.
But also on tables not so big, say *only* 100 Megabyte.
I have also frequent corrupted CDX indexes.
I discovered this corruption not by mean of a Foxpro error, but only
executing a test program that loops throughout the records in the DBF
on every tag in the index.
If the problem is a faulty network, know of a way to trace the network
error/problem?
Thanks in advance for the attention.
Records looks deleted in the browse window but in fact they aren't
(and they don't process as if they are.)
If I look at the DBF file (in ASCII), I see that an asterisk/space
(asc. 42 and 32 respectively) is used at the beginning of the records
to represent whether or not they are deleted.
If I look at the faulty records, I see that they have ASCII 26 instead
of ASCII 32.
Does anyone know why this may happen?
If I browse the tables in Visual fox, they don't look deleted like
they do in 2.6a.
I have this problem on some very big tables!
For big I mean approx. 1 Gigabyte DBF.
But also on tables not so big, say *only* 100 Megabyte.
I have also frequent corrupted CDX indexes.
I discovered this corruption not by mean of a Foxpro error, but only
executing a test program that loops throughout the records in the DBF
on every tag in the index.
If the problem is a faulty network, know of a way to trace the network
error/problem?
Thanks in advance for the attention.