We're accustomed to a combination of DataAreaID (we have 2, one for each of our 2 companies) and TransID being a unique identifier, but suddenly in a few cases on our ProjPostedTransTable table, it's not.
There's a set of 2 seemingly unrelated projects, and within that two different ProjIDs are duplicated.
Is that normal, i.e. the combo of DataAreaID & TransID is not necessarily unique?
Or is it indicative of something being amiss?
We use this table in joins, so it's causing a few duplicated rows. I can include ProjID on the join - and that fixes things right now, but I pulled that out of my hat, and am not sure if that's actually the appropriate join.
(Apologies if this is a table specific to our vendor - they think it's a MS-native table, I don't see it in the documentation, but am not sure. )
Edit:
Agh, had typed in wrong table name - changed in title and message body.
Also I think...the combination of DataareadID and TransID is not necessarily unique across the system - they had been in our system, but that was only a coincidence thus far.
But they are and will continue to be unique within a given ProjTransType?
