F2O New version uploaded

[Cal Learner]

Latest upload is f2o_beta12.zip.
It's highlight is fixing a bug in F2O_DBgather.py

So if you had a deficiency or crash using  F2O_DBgather.py, please try it.

As usual, the file is in https://drive.google.com/drive/folders/1-4fBbRxaPhNYZK0gNHuZ3n-Bdoncy2aR

[Ken H]

Just ran F2O.py for the first time after modifying things to point at the right locations.  Came up with the following error message:

F2O Fidelity-specific CSV 2 OFX converter  Dated 2026/01/31 11H_OPT2

Traceback (most recent call last):

  File "F2O.py", line 19, in <module>

    from dateutil.parser import parse

ImportError: No module named dateutil.parser

Python detected an error during execution of f2o.py program. Note error message above.

Press any key to continue . . .

I think I'm really close, but don't know what the error means.  

[Cal Learner]

Line 19 is "from dateutil.parser import parse"

My ActiveState Python 2.7.18 came with dateutil. For other Python, that may involve "pip"

[zanzibar743]

ActiveState no longer exposes a public, static direct-download URL for the ActivePython 2.7.18 Windows installer; their docs now route you through the “State Tool” instead. Because of that, there is no reliable official .exe or .msi link I can give you that will still work today.

What you can do instead

Use the State Tool to get ActivePython 2.7.18 on Windows (official method): in an elevated PowerShell run

IEX(New-Object Net.WebClient).downloadString('https://platform.activestate.com/dl/cli/install.ps1')

then in cmd.exe run state activate ActiveState/ActivePython-2.7 to download and create the 2.7 environment.

All well and good with running the State Tool, except the activate command doesn't work.  

C:\Users\zanzi>state activate ActiveState/ActivePython-2.7

█ Creating a Virtual Environment for your Project's Packages

 x The requested project ActivePython-2.7 does not exist under ActiveState. Please ensure the owner is correct and that

the project has been created.

--
You received this message because you are subscribed to the Google Groups "Microsoft Money" group.
To unsubscribe from this group and stop receiving emails from it, send an email to microsoft-mon...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/microsoft-money/9400e28e-d2b4-48b4-b911-e14ff0859b9dn%40googlegroups.com.

[Cal Learner]

I see the download page link is dead. 

I still have 09/30/2022  10:55 AM         5,742,592 ActivePython-3.7.msi sitting in my downloads folder.

I Googled the SHA1 and SHA2 for that file, but no hits. Also no google hits for "ActivePython-3.7.msi".

https://sites.google.com/site/pocketsense/home/msmoneyfixp1/p2 has comments on installing Python 2.7x... He mentions Anaconda. 

But your current Python 2.7... what is it? Can you find pip? That may be your best bet.

If I try to port to Python 3, the problem is that I don't think it has a compatible hash.  I use hash to create the FITID. But if there is no available 2.7.x, I guess I could work on that. If the hash is different, well... that could be dealt with.

But try yours, and if not that, I would check Anaconda.

[zanzibar743]

Thanks for the info. I have the python.org distribution. I'll work on getting pip to install the utility. I need Python 2 for pocketsense so no need to try to port F2O to Python 3

To view this discussion visit https://groups.google.com/d/msgid/microsoft-money/54873764-1d54-4349-9eae-17931bf7daf9n%40googlegroups.com.

[Dan Adkins]

The file download link for ActiveState Python 2.7.18 installer is available on my blog.  See:   Links to Alternatives and Solutions thus far

To view this discussion visit https://groups.google.com/d/msgid/microsoft-money/54873764-1d54-4349-9eae-17931bf7daf9n%40googlegroups.com.

[Cal Learner]

I had posted about a problem and workaround, and have deleted the post. The problem did not exist with versions I had uploaded, I am glad to say.

[Cal Learner]

f2o_beta13.zip has been uploaded. F2O.py has been updated including corrections. recent_note.txt is a new addition to the zip file. Here are the contents:

The beta12 was working well for most people. The beta13 F2O.py adds better handling of some things, particularly DEBT. Observe.

For those interested, it can be possible to edit the  F2O_cfg.py with a spreadsheet program for use with F2O.py but not with  F2O_DBgather.py. Most are done with  F2O_DBgather.py early in the process. The problem occurs mainly in the CUSIPS into numbers... leading zeros removed, and a CUSIP with an E in it treated as a big floating point number. I used to be worried about quotes (") characters being introduce, but those seem to not cause a problem in my trials.

Sometimes a CUSIP will have a duplicate, such as when a security changes symbols. Barrack used to have symbol GOLD, but is now B. So two entries are fine.

If you use DEBUG=1 or more, you may get a file log_qq1.csv appearing. Feel free to look at it or delete it.

It shows transactions that ended up not being used. This file has the account name and number redacted to the last 2 characters, in case you want to share a line or two from that file.

I use that to see what is not being handled yet.

Cal Learner 2026/2/6

[Cal Learner]

beta13A.zip adds making <NAME> not be "No Description", but instead makes name for Money to be able to remember for category.

[Cal Learner]

f2o_beta13E.zip uploaded... It does what 13A was supposed to do.  

[Ameridan (microsoftmoneyoffline.wordpress.com)]

I added an icon in my article to make it easier to access Cal's F2O download folder.

[Marc]

Where can I find your blog with the links?

On Monday, February 2, 2026 at 7:36:35 AM UTC-6 Ameridan (microsoftmoneyoffline.wordpress.com) wrote:

[Ameridan (microsoftmoneyoffline.wordpress.com)]

https://microsoftmoneyoffline.wordpress.com

[Dharmendra]

Marc,

https://sites.google.com/site/pocketsense/home/msmoneyfixp1/p2

To view this discussion visit https://groups.google.com/d/msgid/microsoft-money/8c944b26-10ba-4990-bbae-2b23d18d0469n%40googlegroups.com.

[Cal Learner]

F2O_beta14.zip uploaded.

This makes several improvements, and I would encourage using at least the F2O.py from that zip file. Do that especially if there is anything about your F2O operation that seems to need improvement. Reminder, there is no installation process. You should be able to replace files with the same name in your F2O folder with the files from the F2O_beta14.zip. The zip does not contain a file named  F2O_DB.csv or  F2O_cfg.py although it does contain example files with filenames that start with those names. Those are the two files that you should maintain backups of.

[Cal Learner]

F2O_beta15.zip uploaded.

A new file recent_note.txt describes the use of the new mk_F2Ops.bat.py file. It is for the F2O+PocketSense user who want the process to be quick and easy once set up. notes_on_F2Ops_batchfile.txt adds detail. It generates F2Ops.bat, which runs F2O and then PocketSense without interaction.

Added a specialized feature to not generate OFX files for specific Fidelity accounts. To use this, into your F2O_cfg.py add this line using your account numbers instead of the examples.
F2O_IGNORE_ACCOUNT=["X12345678","Z87654321"]
If F2O_IGNORE_ACCOUNT is not present, F2O produces OFX files for each Fidelity account.

That is described at the bottom of recent_note.txt and in F2O_optional_advanced_info.txt. Few will benefit from this one. The batch file thing should have more general use.

[Ameridan (microsoftmoneyoffline.wordpress.com)]

Nice job on the mk_F2Ops.bat.py  Before I try out the resultant F2Ops.bat  -  does the 4Y file memorize your responses, or is it a fixed 4 yes'es?  my getdata involves entering a password, so that would be 2 yes'es and a password.  I'm not sure what the 4th yes is for?

[Cal Learner]

Fixed 4. Having more than needed is not a problem generally.

I don't use a password for PocketSense, so I wasn't even thinking about that. I should have mentioned that while writing.  I expect  that 3 lines would have been enough. I guess you could have your password/key encoded in your 4Y.txt (or use a different name) or have it wait for intervention at the time when the password is being requested. The easy way to do that would be to have just 2 lines in the 4Y.txt. What happens if you enter the wrong password a couple times? Do you then get a chance to add the right password? If so, 3 or 4 lines in 4Y.txt could work. So an accidental automatic feature that lets you enter a  password if needed.

My past batch files have used "lines.txt" that just had 4 crlf newlines. Batch files have some quirks, and some things are surprisingly hard to do. My first plan was to add lines.txt into the zip file. I did mull alternatives in that area. Since Yes is the default, blank lines work to take the default.

[Ameridan (microsoftmoneyoffline.wordpress.com)]

Your  accidental automatic feature worked out fine after all.   It prompted me for password, I entered it, and the script resumed.

Those that don't want to manually create a bat file should appreciate your mk_F2Ops.bat.py script!

I'll add this to the F2O.bat section of my article :)

[Cal Learner]

Beta15A, just uploaded,  handles cases where you do the same thing on the same day, such as buy a coffee at the same store as you did earlier in the day. Before, it would generate two transactions, but both had the same FITID, so Money ignored one.

It was always intended that that would work properly. Now it does.

[Cal Learner]

Beta15B.zip has changes in  F2O.py and particularly mk_F2Ops.bat.py.

mk_F2Ops.bat.py should now generate a better F2Ops.bat file.

[Cal Learner]

Beta16.zip uploaded.

Getting close to calling it version 1.0. No known bugs.

The latest thing addressed in this release is that the Fidelity Accounts_History*.csv files have a Price column. Using that number, which is rounded to the nearest cent (0.01), for the <UNITPRICE> value would sometimes cause Money to see an inconsistency. It would quietly ignore the transaction.  By computing the  <UNITPRICE> values, that problem does not exist. DEBT (such as Treasuries, bonds) also has that <UNITPRICE>  field. Those prices are in percent of par.

[-Kevin N]

Hi Cal,

I think it was beta_15c where you introduced the feature of removing the Memo field data.

Q. Is there an entry that can be made in F2O_cfg.py (or any other means) so that the Memo field data could be included as it was before?

-Kevin N.

[Cal Learner]

Kevin:

A new optional value can be input via F2O_cfg.py:
VERBOSE_MEMOS=0 #gives minimum MEMOs.
VERBOSE_MEMOS=1 #adds memos for things that do not have symbols. Not sure if this turns out to be useful.
VERBOSE_MEMOS=2 #provides maximum MEMOs.

2 is pretty much like the previous. 

[-Kevin N]

Hi Cal,

VERBOSE_MEMOS=2 works perfectly.

Thank you.

-Kevin N.

[Ameridan (microsoftmoneyoffline.wordpress.com)]

F2O article updated to reflect 15B and 16 additions.

https://microsoftmoneyoffline.wordpress.com/2024/02/03/cals-fidelity-specific-csv-to-ofx-converter/#5

[Cal Learner]

A person had Money reject the OFX files from F2O. The cause was determined to be unescaped ampersands in the F2O_DB.csv database file.

I had made more documentation on how to edit the F2O_DB.csv file to deal with getting rid of the  the ampersands, but I then modified F2O.py to do that for you by default. It now will actually edit your  F2O_DB.csv,  if needed, to change unescaped & into &amp; .   Besides modifying F2O.py (now dated 2026/3/23), I updated some documentation a bit.

Download F2O_beta16A.zip, and overwrite your existing files from that zip file. No files in the zip files are named the same as your customized files. Your customized files are  F2O_DB.csv, and optionally F2O_cfg.py and F2O.bat

There is no change in behavior from beta16 for people who did not get the problem.

Reminder: find the zip files in https://drive.google.com/drive/folders/1-4fBbRxaPhNYZK0gNHuZ3n-Bdoncy2aR

[Ken H]

Hi Cal,  I'm finally back in the US and over jet lag. F2O has been working flawlessly until today. I did an options trade yesterday and today, when I ran F2O, it wanted to add the symbol to the db.csv, but didn't give me the choice to identify it as an option. The choices were MF, stocks, etc., but not OPT. I've been using beta12 because it worked, but I just tried beta16a. It gave me the choice of OPT, but I now get the following error message:

Proposed ticker presented is TSLA260821C480

Positions entry has name is TSLA AUG 21 2026 480 CALL

Can now add a new F2O_DB.csv entry. If 401k suggest MF

Inputs are not case-sensitive. Do not use quote characters, but do press Enter.

Enter one of ('MF', 'STOCK', 'OTHER', 'OPT', 'DEBT') :opt

Traceback (most recent call last):

  File "F2O.py", line 1315, in <module>

    SecDB_index=  findTickerInSecDB( symbol) #shared function

  File "F2O.py", line 314, in findTickerInSecDB

    xx=input("Enter one of " +str(ok_db_types)+" :") #change raw_input to input if python 3

  File "<string>", line 1, in <module>

NameError: name 'opt' is not defined

Python detected an error during execution of f2o.py program. Note error message above.

Press any key to continue . . .

Any ideas? 

As always, thanks for your help.

[Cal Learner]

 F2O_beta16B.zip uploaded and earlier versions removed.

I had been playing with Python 3 to investigating F2O running on either Python2 or on Python3., and I somehow had accidently put some python3-only code into F2O.py starting with beta16. This bug only affected people who had new listed options.