Calls Consolidation went awry!

Nylis G. Renschler II ( (no email) )
Sun, 4 Jan 1998 20:11:23 +0100

Well I did the first EOM billing cycle since trying out the Emer 2.2 and =
something went awry.

My calls table was trimmed upto 1 Jan 98 no matter when a persons =
anniversery date was.
Question: When I put the 2.2 on should I have dropped the original =
stored proc. callconsolidation script and put a new one on?? I did run =
updtabs and instproc. I did not rerun any of the other inst...sql files =
as I was under the impression that was not neccessary. Was I wrong?=20

Dale I did foloow your instructions on doing the seperate table =
calldetails and it still has the records in it. I went back and ran some =
update scripts I wrote to back fill to 1 Dec the calldetails for just =
such a catastrophie but I would hat to have to back fill into calls!!!! =
It was easy going the one direction but I don't think it will be so easy =
going the other way.

What went wrong? I ran the calls consolodation last month on 1 Dec, so =
everything was deleted from 1 Dec to 31 Dec this month.

One thing I find funny is that a customer that has an anniversery on 13 =
Dec and has over time shows a charge on his bill with 12/13/97 usage =
hours... Then I go to his Time On and it shows no hours prior to 1/1/98 =
eeeeeeekk! I about had a massive heart and lung failure!!! If I did not =
have the callsdetail table I would have!

Sorry about the book,

Nylis G. Renschler II
Silyn-Tek Communications