IIF format
7 messages in this thread
I just upgraded from QuickBooks for DOS to Windows. Data point for all DOS
afficianados: my old \QBOOKS directory tree consumed about 5 megs of hard disk,
the new \QBOOKSW directory takes up 15 meg with the converted data files.
I've found a buglet in the Help file. When I go to "I" in the Index, the
second item there is "IIF specification." When I click on it, it jumps to
"Specifying headers and footers."
Where can I find out about the IIF file format? I've got a few home-made
utilities that parse and massage data from the QIF files from the DOS version,
and now they're apparently useless. Is there a developer kit or a doc file for
IIF?
(I did find the various documents in the library here. Is this the width and
breadth of IIF docs? )
John,
Thanks for pointing that out. I will forward the details to the engineers for
their review.
You can access information about IIF files with the following:
Click on the Help icon, then click on "QB Printing, file operations,
preferences", then click on "Transferring data" — the screen that
will follow will have all topics pertaining to IIF files.
Veronica B., Intuit Technical Support, QuickBooks for Windows
Thanks for the alternative path to this document.
Do you know of any third-party tools for massaging IIF data? Do many customers
ask for enhancements that mighe be better served with external tools?
(I'm a fellow software developer, and I'm always looking for new ideas. 🙂
For example, I've made my own tools for extracting the customer list and
breaking the freeform addresses into fixed fields for import into other
database programs, for example, DeskTop Set, a PIM. This lets me move new
customer information quickly into DTS.
John,
I'm sending out demo's of just such a tool would you like a copy ?
Steve
John,
This has been discussed recently, and some of the other users here can let you
know what they have available. Designing your own application to handle
situations that arise to work with QuickBooks is (in my personal opinion) a
great way of dealing with these. One problem as a large market developer is
that there is only so much time and people available for development and
changes have to be prioritized. So, some features, even though they might be
relatively easy to implement, don't get added just because there isn't
time/resources available for writing and testing the changes. I'm not entirely
sure of the legal aspects of producing such tools (I know there aren't any
problems if it is free and the documentation specifically states we aren't
responsible in any way, etc….). See my previous post (#87810 ) on this.
Thanks,
Chris Mohney Intuit Technical Support, QuickBooks for Windows Sysop