Because of past problems with Emerald, I still hand check the emer_out.txt
file before charging the credit cards. On two completely different PC's
that do the BatchOut(one is a new Celeron 333/NT4, the other an old AMD
133/Win98) the emer_out.txt file seems to have occasional corrupted credit
card numbers.
I have noticed this while spot checking the credit cards. Approximately one
in a thousand credit cards listed in the emer_out.txt file is off by one
digit. The emerald database always shows everything to be correct. But the
emer_out file has the credit card number listed with a digit wrong.
Unfortunately, I have been unable to exactly repeat this bug because you can
only Batch-Out once. Is there any way to setup a test so I can Batch-Out
several times (without Emerald Updating the database) and find out if the
corruption is at the same spot in the output file? I'd really like to
isolate this bug.