A bit of history:
I installed my emerald 2.2 - 2.5 upgrade back in Jan 1999 and from that time
forward I could not consolidate, after using various versions of Emerald and
much messing around I decided to wipe my 2.2 - 2.5 upgraded database out and
install Emerald and customer data fresh thinking that 2.2 - 2.5 upgrade data
was the real problem, WRONG the new version would not consolidate either. as
a by product we used to write out the emerald data base to a text file this
stoped back in Jan 1999 in May I discovered that having an expire date was
mandatory to writing out the text file so in went the Expire date even
though an expire date is incompatible with the way we wish to do business. I
am sure in my own mind that adding in the expire date is part and parcel to
doing a consolidation however my results are at best a half result.
My steps to consolidation:
1. Around the 4-5 / June 1999 I down loaded emerald25.exe from
ftp.iea-software/emerald
2. I uninstalled Emerald and Radius from my production machine but left the
emerald data intact.
3. I deleted the emerald/radius directory (so no previous programs were
going to interfere)
3. I re-installed Emerald and Radius using the emerald25.exe
4. I went in to Emerald Admin and ran /Database /Maintenance /Check Database
5. I also ran the Update calls table from the same menu
6. I then went in to emerald and ran from the batch menu Pre Invoice Summary
and finally Charges.
As my original e-mail indicates the dates for consolidation were all screwed
up instead of the being for April / May my consolidation gave me dates of 5
Jan 1999 (05/01/1999) and 6 Jan 1999 (06/01/1999) instead of 01/05/1999 and
01/06/1999.
Hope this helps
Regards David Moore
moored@romtech.com.au
----- Original Message -----
From: Annabel Mwansa <amwansa@zamnet.zm>
To: <moored@romtech.com.au> <emerald@iea-software.com>
Sent: Monday, 7 June 1999 11:05
Subject: Re: [Emerald] Problems in call consolidation
> Hi,
>
> We are running Emerald 2.5.267. Consolidation runs without any errors.
> The Calls history, however, is not updated and neither is the status
> field in the calls table.
>
> We were able to consolidate using Emerald 2.1/2. We've never been able
> to consolidate since the upgrade to 2.5. I've tried creating a fresh
> database using Emerald 2.5 but get the same result.
>
> David, (and anyone else who has been able to get consolidation to work),
> could you tell me what version you're running? How did you get it to
> consolidate? We've had this problem for too long and would really like
> to see the system work as it would solve quite a lot of our problems.
>
> Please HELP!!
>
> Regards
> Annabel
>
> ************************
>
> I ran a call consolidation on June 6, 1999, the call consolidation ran =
>
> all the way through but when I look at the call history records the =
> month and day are revesed ie the the history record is 1st of January =
> 1999 instead of 1st of June 1999. see records below.
>
> p.s. we are using DD/MM/YY has this something to do with our problem how
> =
> can I fix the problem.
>
>
> AccountID StartDate Months Mins Calls
> =
> ChargeID =20
> ----------- --------------------------- ----------- ----------- =
> ----------- -----------=20
> 3 1999-01-06 00:00:00.000 1 45192 23
> =
> NULL
> 7 1999-01-05 00:00:00.000 1 1987 1
> =
> NULL
> 7 1999-01-06 00:00:00.000 1 35436 10
> =
> NULL
> 8 1999-01-06 00:00:00.000 1 43373 12
> =
> NULL
> 9 1999-01-05 00:00:00.000 1 7 2
> =
> NULL
>
> Regards David Moore
> moored@romtech.com.au
>
>
>
>
>