[Emerald] Importing a calls table

David Moore ( (no email) )
Sun, 2 May 1999 08:49:12 +1000

This is a multi-part message in MIME format.

------=_NextPart_000_0010_01BE9478.A6856920
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I have killed my 2.2 on (SQL 6.5) to 2.5 upgraded version of emerald. =
Reinstalled SQL 7 and installed the production version of emerald, I =
have re-keyed all the users and wish to transport the old calls table =
and Call history, SQL 7 has the capability to export to Excel which I =
have done. I have exported the calls tables taken out erroneous entries =
and generally massaged the data.=20

I had to do this because consolidation did not work at the end of each =
month. What I intend to do is copy the callshistory table from the old =
system in to the new system. This table stops in December because of the =
consolidation problems I intend to restore all of my calls records =
export them add them all together de duplicate them and re import them =
into the new emerald 2.5.

I have noticed that generally the records start with an AcctSessionID of =
1 and stop with an AcctSessionID of 2 some records don't have the =
corresponding start or stop record, ie have an account session of 1 but =
no stop record or have a stop record but no start record if I import =
this table will I have further problems or will the consolidation =
procedure ignore the errant records.

Regards David Moore
moored@romtech.com.au
=20

------=_NextPart_000_0010_01BE9478.A6856920
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

I have killed my 2.2 on (SQL 6.5) to 2.5 upgraded =version of=20emerald. Reinstalled SQL 7 and installed the production version of=20emerald, I have re-keyed all the users and wish to transport the =old calls=20table and Call history, SQL 7 has the capability to export to Excel =which I=20have done. I have exported the calls tables taken out erroneous entries =and=20generally massaged the data.
 
I had to do this because consolidation did not work =at the end=20of each month. What I intend to do is copy the callshistory table from =the old=20system in to the new system. This table stops in December because of the =consolidation problems I intend to restore all of my calls records =export them=20add them all together de duplicate them and re import them into the new =emerald=202.5.
 
I have noticed that generally the records start =with an=20AcctSessionID of 1 and stop with an AcctSessionID of 2 some records =don't have=20the corresponding start or stop record, ie have an account session =of 1 but=20no stop record or have a stop record but no start record if I import =this table=20will I have further problems or will the consolidation=20procedure ignore the errant records.
 
 
Regards David Moore
moored@romtech.com.au
 
------=_NextPart_000_0010_01BE9478.A6856920--