guanlisheng wrote:If i was a end user, i don't except one standalone tool to import any thing... therefore better to integrate it with existent product.
I understand, I don't have the skill set or time to re-write for C++ code though.
This is just something I use to make my life easier and thought I'd share it in case it helps others.
guanlisheng wrote:Besides programing language difference, why we need table schema modification here ? logically, current schema is suitable.
OFX uses a unique identifier for a transaction (per account). Using that means you can be sure to import each transaction only once. The addition is a column called FITID (named after the value in the OFX file). There isn't a field for that in the current schema.