RE: [Emerald] Credit Cards revert to Renewals

Leah Bilan ( Leah@TDI.NET )
Thu, 13 May 1999 22:14:23 -0400

We use .227 and everything works ok, except when you batch back in it gives
an error. This we just override and it marks everyone paid when we hit OK.
At the end of the batch we select cancel so that it doesn't erase all input
to our cc file. This is about the only small problem that is worth living
with, with this version. However, consolidation we still have problems with
in this version. Using 263 was to much of a pain with over 4000 customers
with changing cc back to renewals. Not fun for me!!!


> -----Original Message-----
> From: David V. Brenner []
> Sent: Thursday, May 13, 1999 10:03 PM
> To:
> Subject: RE: [Emerald] Credit Cards revert to Renewals
> > >I had this same experience with emerald and paid a $250 phone call to
> > >support with Sheryl and still to this day waiting for a reply to my
> > >problems.
> > >We did revert back to .227 because of this problem.
> Dale:
> I keep hearing about this credit card problem with Emerald with builds
> later
> than 2.5.224 and although we are not to the point where we are running
> cards
> with it yet, we would like to at some point.
> We are running 2.5.263 on a couple of machines and Sheryl installed .227
> on
> the machine where SQL is, plus at least one other machine has a different
> version installed.
> I would like to make things consistent, but I want to know which version
> is
> the most stable *and* supports credit card issues properly. Should I be
> using a lower revision? If so, which one should I use and where can I get
> it?
> _______________________________________
> David V. Brenner -
> International Services Network Corporation