Ofx import from Mono based Command Line App

General discussion on all other topics under the sun.
Post Reply
thompsonson
New MMEX User
Posts: 8
Joined: Sat Sep 01, 2012 9:32 am
Are you a spam bot?: No

Ofx import from Mono based Command Line App

Post by thompsonson »

Hi All,

I've updated the command line app i use to import OFX data into MMEX. It should now be cross platform with Mono (only tested on Mac OS so far).

Binaries and usage info can be found here:

https://sourceforge.net/p/mmexnet/wiki/Home/

The code can be found here:

https://github.com/thompsonson/OfxToMmex

Woud love to hear back from people if there are using it or reason why they don't use it :)

All the best,
Matt

guanlisheng
MMEX Developer
Posts: 205
Joined: Wed Dec 21, 2011 5:58 am
Are you a spam bot?: No
Location: China
Contact:

Re: Ofx import from Mono based Command Line App

Post by guanlisheng »

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.

thompsonson
New MMEX User
Posts: 8
Joined: Sat Sep 01, 2012 9:32 am
Are you a spam bot?: No

Re: Ofx import from Mono based Command Line App

Post by thompsonson »

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
MMEX Developer
Posts: 205
Joined: Wed Dec 21, 2011 5:58 am
Are you a spam bot?: No
Location: China
Contact:

Re: Ofx import from Mono based Command Line App

Post by guanlisheng »

Besides programing language difference, why we need table schema modification here ? logically,  current schema is suitable.

thompsonson
New MMEX User
Posts: 8
Joined: Sat Sep 01, 2012 9:32 am
Are you a spam bot?: No

Re: Ofx import from Mono based Command Line App

Post by thompsonson »

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.

guanlisheng
MMEX Developer
Posts: 205
Joined: Wed Dec 21, 2011 5:58 am
Are you a spam bot?: No
Location: China
Contact:

Re: Ofx import from Mono based Command Line App

Post by guanlisheng »

In this case, transaction number is preferred here.

thompsonson
New MMEX User
Posts: 8
Joined: Sat Sep 01, 2012 9:32 am
Are you a spam bot?: No

Re: Ofx import from Mono based Command Line App

Post by thompsonson »

guanlisheng wrote:In this case, transaction number is preferred here.
Yeah, I'd considered that but it's editable. The FITID isn't something that should be changable.

I think the transaction number is used for cheque numbers as well; that's how I'd used it in the past at least. Hardly write a cheque now though!

Post Reply