1

Closed

Can't make it work

description

Thanks Andy.

I'm glad this works for you, but I'm afraid that my lack of understanding of the coding/command issues means that my attempts to follow it don't result in an ofx file in the folder to which the csv file has been downloaded (clearly my fault, although I did manage to make the hleOfxQoutes package work!).

Specifically, this is how the top of my Command file looks:
set PROGRAM=D:\Users\John\Desktop\Money FT quotes\csv2ofx.exe
set DOWNLOAD=D:\Users\John\Desktop\Money FT quotes
Is that right? Does the remainder need amendment?

Do I need to use the cmd window/prompt? If so, how do I cause it to address the file path above?

Do I need to amend the config file from that I downloaded from your site? [I have put it in the System 32 file in C:\Windows\ - is that right?]

Would it be asking too much to post a set of simple instructions on a step-by-step basis which don't assume computing knowledge?

I've posted this on the Google site too.
Closed May 3, 2014 at 6:33 PM by gbjbaanb

comments

gbjbaanb wrote Apr 11, 2014 at 9:39 PM

Only the top 2 lines need amendment to refer to where you've put the program.
When you've done that you can run it in explorer by double-clicking it. It will pop up a command window, run the conversion (you should see it print out a line for each stock converted) and then close - leaving a new .ofx in the same directory as the csv.

You only need to use the config file if you need it to increment a unit count for each share - Money 2003 apparently needs that for ofx imports - ie to recognise that the 'statement' has new values. If you're using Sunset or 2005 then you do not need the config file. If you do need the config file, put it in the same directory as the .cmd file you click on (or the directory the .exe is, I forget which).

You can, of course, run it in a command window by typing out the options in full. This can be a good way to test that it works, as the command window remains open afterwards so you can see if it prints out any errors. Remember to use the --debug 1 option.