F2O error 42 and other update info.

[Cal Learner]

It turns out that not only are the Fidelity  Accounts_History*.csv columns and headers not the same for everybody, the Portfolio_Positions*.csv files can differ also.

If you get "now to invoke the debugger error 42" when you run F2O.py, that would be the probable cause. 

I uploaded  f2o_beta11F_RC2.zip which should deal with that. It gives the same OFX as the previous for me, but that is because Portfolio_Positions*.csv have the columns and column headers in the place that I was thinking everybody had.  So if F2O is working OK for you now, no need to change for now. Somebody who ran into error 42 is trying that, and if that looks good, I will probably 

Still to come is handling listed options better. 

[Ameridan (microsoftmoneyoffline.wordpress.com)]

I just noticed this settings screen, which might be a recent thing, that may account for the variances, if they also affect the export.

[Tom Meyer]

Something for consideration.

  Yes I have both 2.7 and 3 which makes me edit the f2o.bat on each update.

• Using the Python Launcher (py.exe):
  • The Python Launcher for Windows is installed by default with Python 3.3 and later and is usually located at C:\Windows\py.exe.
  • You can run specific versions from the command line using py -2.7 for Python 2.7 or py -3 (or py -3.x) for Python 3.x. 

--
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/334150c9-06b9-42b8-9c9f-4b0bb21305a9n%40googlegroups.com.

[Ameridan (microsoftmoneyoffline.wordpress.com)]

Tom, Cal will probably never update F2O.bat, so just rename your modified version to F2O_tom.bat, and point your shortcut to that instead.

Cal, the settings I mention above is offered in Fidelity's Positions tab, but I haven't played with them to see if they affect the export file.

[Cal Learner]

I have a python.bat file, which does python 2.7 and a p3.bat file which has
To run xyz.py  with Python3, I do p3 xyz.py 

 =======begin p3.bat=================
@set pythonhome=
@set pythonpath=
C:\apps\python\WPy64-31160\python-3.11.6.amd64\python.exe %1 %2 %3 %4

========== end python3.bat =============

I can do Python 2.7 with python xyz.py .

Right now, Python 2.7 is my default, so I can also just type xyz.py 

The hash algorithm, which is used to generate the FITID, is the reason F2O is only written to work with Python 2.7 so far. I do occasionally look up methods to hash with either.

On Wednesday, January 28, 2026 at 7:53:40 AM UTC-6 tom.h...@gmail.com wrote:

[Cal Learner]

I had not noticed that Positions Settings thing before, and have not checked to see if the CSV file might be affected negatively. 

[Cal Learner]

Good point... right now F2O.bat is provided in the beta*.zip files, and I should probably instead provide  F2O.bat.sample1 so as to not overwrite people's customized F2O.bat.