I did this yesterday, but haven't heard back from anyone yet. In the
meantime, can we re-"batch in" the same batch-in.txt file or will it create
duplicate payments in Emerald, etc.?
If I need to remove the entries in the file that pertain to
already-processed-by-emerald transactions, I can do that pretty easily since
there weren't many that made it through in the first place.
We need to get them entered in before the end of the month or our monthly
accounting will be all messed up.
> Josh Hillman wrote:
> > Yesterday for unknown reasons, Emerald 2.5.322 failed to import several
> > dozen successful CC transactions that took place that day. Any idea why
> > this would happen? This is the only time it's ever happened. PC
> > had no problems and both the export/import files look completely normal.
> > For 3/28/00, the first 41 transactions have ProcDate IS NOT null. Of
> > 5 have TransType=3. All others are 4.
> > For 3/28/00, the last 88 transactions have ProcDate IS null. All of
> > have TransType=2.
> > The batch-in.txt file contains 129 normal-looking records.
> > If I hit "Batch In", using the same import file that it used yesterday,
> > it mess up anything?
For more information about this list (including removal) go to: