As I noted earlier, CR 6.0 can edit CR 5.0 invoices (and CR 5.0
engine can print CR 6.0 reports).
> >> Next: If we delete an invoice instead of voiding it, and re-create it,
> >> that customer will NOT get a bill the next month. OK so we now only void
> >> invoices "REMOVE THE DELETE OPTION".
> >If you delete an invoice, Emerlad doesn't move the expiration back.
> >Voiding does. Just move the expiration back and it will re-invoice
> >the customer.
> That's OK for that month, But the following month the customer does NOT get
You would have to give me a specific example. The only reason why
Emerlad will not invoice a customer (besides they are inactive
or don't have any services) is because there is already a non-voided
invoice for the period.
> >Logging in is pretty cut and dry. If an account is inactive, that
> >account doesn't log in. I'm guessing that either you have two MBRs
> >that you are looking at, or are missing the extension/limit field.
> That's what you said the last time, but I AM NOT SEEING THINGS.
Atleast I am consistent. :) If you have a specific example of
an expired user in your database that is getting authenticated,
then I can attach to your database and explain to you why the
users is being authenticated.
-- Dale E. Reed Jr. (firstname.lastname@example.org)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com