Maybe if this route is taken, the Overwrite option can also back up the file
it's about to overwrite (like 0002021302-batch-out.txt or whatever).
The big problem with credit card batching is that everyone's using different
programs that all behave differently, and from what I can tell, most of
those programs were written very poorly (e.g. still written for Windows
3.1x, but "works in Windows 95, 98, NT").
Josh
----- Original Message -----
From: Dale E. Reed Jr. <daler@iea-software.com>
To: <emerald@iea-software.com>
Sent: Wednesday, February 02, 2000 12:52 PM
Subject: Re: [Emerald] credit card batch-out file
> Ronnie Franklin wrote:
> >
> > IF you named each batch out file to the date... like 020200.out or some
> > other method then the CC program could pick up the file, process it, and
> > export it to batch.in or something.. then Emerald would delete the
bacth.in
> > file just like it does now, but I would not be appending a batch.out
file
> > the next day....
>
> What if you do two batch outs in the same day? Does the first get
> overwrote or appending? If appending, do the transactions get
> double-billed?
>
>
> --
>
> Dale E. Reed Jr. Emerald and RadiusNT
> __________________________________________
> IEA Software, Inc. www.iea-software.com
>
> 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