Accountright Import/Export Bug

The problem with HEX 0A in the data is that the data cannot be easily imported into a database as the continuation of the description is now at the beginning of the next text line (Which normally, in the case of ItemSales data, is the Company Name Field)

The importing of such raw data therefore becomes useless unless it is "cleaned up"

So that's what I have done - Read the export line by line and remove the lonely HEX 0A characters

You may well be correct that the operator may have pressed an enter while keying the description but I do not have HEX 0D0A other than at the end of the line, which I expected

SOLUTION

The trick is to read the file - Scan the file looking for HEX 0A0D together - replace the HEX 0A0D with HEX FFFF - Rescan the file looking for HEX 0A - Replace with a space - Rescan the file looking for HEX FFFF - replace the HEX FFFF with HEX  0A0D

Works for me - perfectly 

A little challenge but all good

Thank you so much for your interest !

I have performed further checking into the HEX 0A character appearing by itself in the line.

I have found that by deliberately pressing the Enter Key in the middle of the ITEM Description, this has no effect on the description when it is Exported.   ie, Pressing the Enter Key does not introduce a HEX 0A to the data.

This therefore confirms my original belief that there is actually an error when the Export Utility is used.

As I said, I have had to write special software to "Clean" the data exported from the Export Utility, and this seems to work.

I am just concerned that normal MYOB users who do not have programming experience will find that the Export Data utility will cause them errors if they attempt to used the exported data  in Excel or perhaps a database like Access.

Thank you for everyone's interest.