Yes, I am using the "id" field.
When I witnessed the strange behavior even valid airborne flights (visible in FS) were showing up in FSInterrogate with the id field as 0x00000000. In some duplication cases both flights had 0x00000000, and some cases both had apparently valid (and duplicate) id's, while still some times flights that were duplicated had 0x00000000 while it's alter-ego (same Flight#) had an apparently valid id.
As you can see, I started losing trust in the "id" field (and losing my mind!). Too many possible id combinations, with no logical way to know which one was right/wrong, valid or invalid. I simply used the Flight# as a visual queue when Interrogating the registers because of this id dilemma.
So far, since my last post... I did have dupes show up again, but failed to re-enact the chain of events that caused it.
If I can come up with a predictable, reconstructable chain of events, with some supporting evidence, I will let you know. I'd rather not just give you just the Interrogated data that shows duplicates, I'd like to give you the events that cause it because I don't want to waste your time any more than I already have.
Thanks again!
Phil