I renamed the original (bad) Calls table to "CallsOld", then ran the script
below (modified from insttabs.sql) and changed the constraint name to
"pk_calls2" from "pk_calls" as you suggested. The new Calls table was
created with no problems.
Then I ran "insttrig.sql" and it responded with:
Msg 2714, Level 16, State 1
There is already an object named 'calls_insert' in the database.
Then I ran "instperm.sql" and had no apparent problems.
Here's the script to create the Calls table that I used:
CREATE TABLE Calls
(
CallDate smalldatetime NOT NULL ,
UserName varchar (32) NOT NULL ,
AcctSessionID varchar (10) NOT NULL ,
AcctSessionTime int NULL ,
AscendDataRate int NULL ,
AscendDisconnectCause int NULL ,
FramedAddress varchar (16) NULL ,
NASIdentifier varchar (16) NOT NULL ,
AscendModemSlotNo int NULL ,
AscendModemPortNo int NULL ,
NASPort int NOT NULL ,
AscendConnectProgress int NULL ,
AcctStatusType tinyint NOT NULL CONSTRAINT pk_Calls2 PRIMARY KEY
(NASIdentifier, NASPort, AcctSessionID, AcctStatusType),
FramedProtocol int NULL ,
AscendFirstDest varchar (16) NULL ,
AcctDelayTime int NULL ,
AcctInputOctets int NULL ,
AcctOutputOctets int NULL ,
AcctInputPackets int NULL ,
AcctOutputPackets int NULL ,
AscendPreInputOctets int NULL ,
AscendPreOutputOctets int NULL ,
AscendPreInputPackets int NULL ,
AscendPreOutputPackets int NULL ,
AscendPreSessionTime int NULL ,
)
GO
Thanks AGAIN,
Josh Hillman
hillman@talstar.com