RE: [Emerald] calls table primary key

Rudy Komsic ( (no email) )
Sat, 27 Feb 1999 00:38:47 -0500

> Put AcctSessionID First. You want the must unique field first, to
> make the index more unique.
> I'm not sure why you can't just re-create the primary key without
> doing all this? Just right click over the table, select properties,
> click the advanced, and change the primary key.
because some of us are unfortunate to the USR's Chassis bug where it does
not increment the first 2 bits in a sessionID, the primary key will always
fail to be created since there are duplicate records. That is why this

For more information about this list, including removal,
please see