Re: Corruption Symbol

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Jonathan,

Here's a brute force work-around suggestion (if nothing else works) if
file is not too large:

First, identify the "bad" character using your hex editor (several
free ones on the internet - Google "free hex editor"). You may need to
convert its hex value to an ascii value (0-255). I use Frhed

http://frhed.sourceforge.net/

which displays the ascii value along side the hex bytes.

Then the hard part - Modify the import part of your code to examine
the file to be imported for that character and delete it or replace it
using one of the VFP functions, e.g. STUFF() or STRTRAN() if a small
file, or use STRTOFILE() and low level functions if a large file. -
You probably know all that STUFF :)

Steve


On Tue, 20 Oct 2009 08:35:50 -0400, "Jonathan Morningstar"
<jonathanmorningstar@xxxxxxxxx> wrote:

This is the short version of an issue that I am having while importing data.

Ya know that thick looking hash mark in corrupted data? What's it called?



Long version... I have one client out of 200 that gets 'bad data' when
importing info from another product. Their data will have "that thick
looking hash mark" in their data and it bonks up the fpt. I am sure it is
some binary character indicating corruption but I still would like to know
the correct naming of this symbol.



On the other hand, how do I trap this and keep it from happening. I have my
'trouble child' making copies of imports before running them into my product
in hopes that I will get a pre-import file to look for some anomalies that
causes this to occur. Any info, help, and/or guidance is greatly
appreciated.



As always

Respectfully,



Jonathan Morningstar

.

Relevant Pages