On 2005-06-02, John Pollard <invalid[at]invalid.com> wrote:
- quote -

That's true. I should have been more careful with my words.
What I meant to imply is that the extensions that Intuit made to
OFX which they called QFX are easily breakable.

But from the point of view of a OFX application, I don't care.
As long as Intuit continues to use an extension of OFX, then it
won't matter to me what they do. Any well written program that
understands OFX should easily understand QFX and continue to do so.
(Just as you say.)

Colin Smale wrote:
- quote -

This is trivially easy to test, you can do it yourself ...
assuming you are in a position to utilize it at all.

Before getting your hopes too high though, I caution you that
Intuit is now aware that this information has been made public:
my guess is that it will not continue to work for long.

--
John Pollard
First initial underscore Last name at mchsi dot com
Please reply to newsgroup

Mark Horn wrote:
- quote -

Just a small quibble with your characterization: I think it is a
bit misleading to say the Intuit has "broken OFX" ... especially
when you follow immediately with the correct statement that "QFX
is OFX". Everything in a QFX file is OFX compliant. The
"<INTU.BID> " tag is specifically allowed for in OFX specs; any
creator of OFX files can acquire (register) a tag name prefix,
then use that to add new fields in their OFX files.

The proof that OFX is not "broken" in a QFX file is that all you
need do is change the extension to OFX and any well written app
that can import OFX files can import QFX files. It is only
Quicken, which is, after all a proprietary application, that
will not process plain vanilla OFX files; apps that can process
plain vanilla OFX can process QFX.

- quote -

--
John Pollard
First initial underscore Last name at mchsi dot com
Please reply to newsgroup

Mark Horn wrote:
- quote -

Can anyone confirm or deny whether this will work for accounts in
currencies other than USD? Assuming the currency in the OFX/QFX file
corresponds to the account in Quicken that is. I have tried something
similar in the past and I seem to remember there was something that
wasn't so straightforward.

--
Remove REMOVE from email address to reach me!

On 2005-06-02, Chris Cowles <NoSpam[at]For.me> wrote:
- quote -

Actually, the only reason that the Quicken folks need to add /
change fields is because Intuit has intentionally broken OFX in
order to get QFX. Basically QFX is OFX. But if Quicken doesn't
see the right combination of fields along with <INTU.BID> , it won't
import the file.

Additionally, Quicken makes a connection back to Intuit, and
provides the value of <INTU.BID> to be looked up. Intuit then
returns back to Quicken the rights that the particular FI has.
If the FI hasn't licensed the right to import that file into that
particular piece of software, then Quicken fails the import.

Basically what the Quicken group's workaround does is add an
<INTU.BID> that seems to have licensed absolutely everything.
This fools Quicken into allowing the import.

I've never even tried it. Just thought the reverse logic may have been
necessary for Money and, assuming so, the information below may have helped
someone.
--
Chris Cowles
Gainesville, FL


"John Pollard" <invalid[at]invalid.com> wrote in message
news:uk%23Rc9sZFHA.1148[at]tk2msftngp13.phx.gbl...
- quote -

Chris Cowles wrote:
- quote -

I only have Money2002, so it is possble that MS has changed the
way importing works since my version; but in M2002, you can
import a QFX file without modifying any of its contents. Just
change the extension to ".ofx" - or, if you want a record that
the file started out as a qfx file, just append the ofx
extension to the qfx extension.

--
John Pollard
First initial underscore Last name at mchsi dot com
Please reply to newsgroup

This was posted on a Quicken forum. I have no use of it, but others may find
value in being able to import QFX into Money. I'm guessing you can use the
converse of this workaround to make it work.
--
Chris Cowles
Gainesville, FL


"Mike B" <mike_bredenkamp[at]attglobal.net> wrote in message
news:422c8244_2[at]news1.prserv.net...
- quote -