Clipper - _DBFCDX/1012 Corruption detected

Author

_DBFCDX/1012 Corruption detected

Lee Clinkscales

2005-03-04, 8:55 pm

I get the _DBFCDX/1012 error when trying to open a DBF file in Clipper 5.3b.

I have not had the problem with other DBF/CDX/FPT files, only with a current
set of files I am trying to convert. I have linked in the DBFCDX libs and
REQUESTed them.

I do not have access to the software that uses these files. This will be a
one-time conversion. I do not need to be able to write to the files. I do
know that these files are used by a POS system called Biz Tracker which used
to be called Nickel Tracker.

Oddly, I have a DBF viewer utility that comes with ZTree. This has no
problem displaying the data (including the odd field below).

There is a field that contains some strange data. It is a 7-character field
where each record's starts with ascii 128d (80h) and contains null
characters (ascii 00) as well as other normal characters.

I have searched Google and looked at the Clipper help file.
If the header is corrupted, I am clueless as to how to repair it.

I have tried Norton FileFix and it has problems with the field with the odd
data.

I appreciate any help you might offer.

Thanks.

Lee Clinkscales

Ross McKenzie

2005-03-05, 3:55 am

On Fri, 04 Mar 2005 20:05:57 GMT, "Lee Clinkscales"
<lee@spamwheelinbikes.com> wrote:

>I get the _DBFCDX/1012 error when trying to open a DBF file in Clipper 5.3b.
>
>I have not had the problem with other DBF/CDX/FPT files, only with a current
>set of files I am trying to convert. I have linked in the DBFCDX libs and
>REQUESTed them.
>
>I do not have access to the software that uses these files. This will be a
>one-time conversion. I do not need to be able to write to the files. I do
>know that these files are used by a POS system called Biz Tracker which used
>to be called Nickel Tracker.
>
>Oddly, I have a DBF viewer utility that comes with ZTree. This has no
>problem displaying the data (including the odd field below).
>
>There is a field that contains some strange data. It is a 7-character field
>where each record's starts with ascii 128d (80h) and contains null
>characters (ascii 00) as well as other normal characters.
>
>I have searched Google and looked at the Clipper help file.
>If the header is corrupted, I am clueless as to how to repair it.
>
>I have tried Norton FileFix and it has problems with the field with the odd
>data.
>
>I appreciate any help you might offer.
>
>Thanks.
>
>
>Lee Clinkscales
>
>

Hi Lee,

So....you haven't tried any Clipper-based application to open/read the
file(s) except your 5.3b creation? If I send you a 5.2e application
using the Six driver, would that help to identify the source of your
problem. It does not necessarily sound like a damaged dbf file to me.

Email me.

Regards,

Ross McKenzie
ValuSoft
Melbourne Australia

valusoft AT optushome DOT com DOT au

Please consider a donation through the Red Cross to our friends affected by the tsunamis.

Sponsored Links