Can any of you MVP gurus out there help me with this one?

I have produced some software which produces OFX files for import into MS
Money.

It is documented that the transaction ID (FITID) must be "unique", but
exactly how "unique" does it have to be to avoid false matches? If a FITID
value is reused after a year for the same account, will that produce a false
match which might cause a transaction to be overwritten?

Thanks in advance,
Colin

Re: FITID Uniqueness in Money OFX files by via_newsgroup

via_newsgroup
Fri Aug 29 14:17:09 CDT 2003

In microsoft.public.money, Colin Smale wrote:

>Can any of you MVP gurus out there help me with this one?
>
>I have produced some software which produces OFX files for import into MS
>Money.
>
>It is documented that the transaction ID (FITID) must be "unique", but
>exactly how "unique" does it have to be to avoid false matches? If a FITID
>value is reused after a year for the same account, will that produce a false
>match which might cause a transaction to be overwritten?

Yes.

Just make the date of the transaction part of the FITID, and that
duplication is not going to occur.

Besides being unique, the FITID must be the same each time that
particular transaction is downloaded.


Re: FITID Uniqueness in Money OFX files by Colin

Colin
Sat Aug 30 05:43:25 CDT 2003

Thanks Cal, now I know what I have to do!

--colin

"Cal Learner-- MVP" <via_newsgroup@please.tnx> wrote in message
news:h59vkv824l97d2v93mk2b23h74k81le2nc@4ax.com...
> In microsoft.public.money, Colin Smale wrote:
>
> >Can any of you MVP gurus out there help me with this one?
> >
> >I have produced some software which produces OFX files for import into MS
> >Money.
> >
> >It is documented that the transaction ID (FITID) must be "unique", but
> >exactly how "unique" does it have to be to avoid false matches? If a
FITID
> >value is reused after a year for the same account, will that produce a
false
> >match which might cause a transaction to be overwritten?
>
> Yes.
>
> Just make the date of the transaction part of the FITID, and that
> duplication is not going to occur.
>
> Besides being unique, the FITID must be the same each time that
> particular transaction is downloaded.
>