Thanks for the info.
Here's an idea that's a bit out of our league:
When Emerald does a batch-out, have it rename the original file (e.g.
batch-out.txt) to batch-out.200002021648.txt or something (I just used the
date/time as an example that wouldn't easily be messed up in any way), then
batch-out the new (batch-out.txt) file. That way, there's a copy of the
previous one and the new one doesn't include any old transactions. Of
course this procedure might be a bit easier said than done...
Josh
> > -----Original Message-----
> > From: emerald-request@iea-software.com
> > [mailto:emerald-request@iea-software.com]On Behalf Of Josh Hillman
> > Sent: Tuesday, February 01, 2000 11:32 PM
> > To: emerald@iea-software.com
> > Subject: [Emerald] credit card batch-out file
> >
> >
> > Is Emerald (2.5.322) supposed to overwrite the batch-out file or is it
> > supposed to append to it? If it's supposed to overwrite it, it
> > doesn't--it
> > appends to it. If someone forgets to delete the file before running
> > batch-out, the CC batching software (PC Authorize, in our case)
> > reads in the
> > new and old transactions in the single file and will process them
> > all unless
> > someone catches it in time.
> >
> > Josh
> >
> >
> > For more information about this list (including removal) go to:
> > http://www.iea-software.com/support/maillists/liststart
> >
>
>
> For more information about this list (including removal) go to:
> http://www.iea-software.com/support/maillists/liststart
>
For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart