Re: [Emerald] CallHistory error

Dale E. Reed Jr. ( (no email) )
Mon, 27 Sep 1999 09:49:39 -0700 wrote:
> I've started getting this error when I run the pre invoice function:
> SQL Server Error: 2627 Violation of PRIMARY_KEY constant
> 'pk_CallHistory' Cannot insert duplicate key in object "CallHistory"
> Can anybody explain it and suggest how it may be fixed?

Emerald puts seperate entries into the CallHistory Table for
Primary, Over, and Toll usage. The DB Schema didn't take that
into consideration for the CallHistory table's primary key.
If you just remove the primary key from the CallHistory
table, the error will go away.


Dale E. Reed Jr. Emerald and RadiusNT__________________________________________IEA Software, Inc.

For more information about this list (including removal) go to: