the CallHistory table appears to have three keys: AccountID,
StartDate and Months - how do I identify the primary key - apologies
if this is all very obvious!
> marcus@redcentre. 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. www.iea-software.com
> For more information about this list (including removal) go to:
Unix Systems Administrator
+61 3 9873 0155
+61 3 9720 7467 (fax)
For more information about this list (including removal) go to: