Look into the QuickBooks SDK, a free download from Intuit. It provides a COM object interface or XML interface to all of the QuickBooks data. Additionally, if you need to do this over a WAN, you can use the QuickBooks Web Connector to talk to QuickBooks asynchronously over a WAN.
QuickBooks integration is not a trivial thing to accomplish. There are many gotchas. Your best friend will be the Intuit Developer Network forums.
You do not want to use QIF, QFX, or IIF exports. They are deprecated formats which can cause data corruption. Additional information about various methods of integrating with QuickBooks can be found on this integration wiki page and on this QuickBooks integration wiki.
Take a look at the QuickBooks SDK. If you want something simpler to work with, QODBC (with the write capabilities), while not free, will probably be simpler to work with for Access.
Google is your friend here. Quickbooks has some primitive import capabilities, but there are a number of small products that do what you need. This guy seems to have some pretty good stuff. Essentially there are a couple of different text formats (QIF and OFX if memory serves) that are used for Quickbooks import, the problem with them is they don't do much error checking. There is also a Quickbooks SDK which allows you to make calls using COM (yum) to import, and that does full error checking (it actually calls into a running version of Quickbooks), but is probably overkill for what you want.
Take a look at Quickbooks SDK and Documentation. The SDK has two COM interface: QBFC and QBXML. The difference in using QBXML, you need to serialize and deserialize XML manually which isn't hard once you get the handle of it. And I find QBXML much more convenient since you can choose to include requests and responses you need.
Also, if you plan to use Quickbooks SDK, the Online Reference is your best friend.
+1 to Yishai. I've been using qodbc for about 10 years now and 4 or 5 different versions of quickbooks. qodbc utilizes a database-like syntax to interact with the company file.
UNLIKE any form of proper database interaction, do as little work as possible in your query itself, as the qodbc driver can take 10 seconds to 2 minutes to handle a dozen records from a table of roughly 1000 records. A process that can import 15 orders with 5 lines each means talking to customer, item, invoiceline, invoice tables and can take 5 minutes. Sadly, I often am reduced to building a MySql database based on mass exports while I sort out and understand the data. THEN I go back and try to make queries directly.
While being an ODBC data connection in windows is great, learn to distrust each link in your toolchain and figure out how to troubleshoot problems to prove aspects positively correct as well as positively wrong. My most recent problem was with QB11 on Win7 x64 computer. The php stack at the time was suspect and was causing errors. And please always try to perform error checking, which is somewhat painful in that environment, but becomes crucial when "something breaks later".
This very minute I'm researching the php stack for win7 to see if I can again trust it for use with qodbc and order importing. (exporting from magento)
发布评论
评论（5）
查看 QuickBooks SDK，它可以从 Intuit 免费下载。它为所有 QuickBooks 数据提供 COM 对象接口或 XML 接口。此外，如果您需要通过 WAN 执行此操作，您可以使用 QuickBooks Web Connector 与QuickBooks 通过 WAN 异步运行。
QuickBooks 集成不是一件容易完成的事情。有很多问题。 Intuit 开发者网络论坛将是您最好的朋友。
您不想使用 QIF、QFX 或 IIF 导出。它们是已弃用的格式，可能会导致数据损坏。有关与 QuickBooks 集成的各种方法的其他信息，请访问此集成 wiki 页面以及QuickBooks 集成 wiki。
Look into the QuickBooks SDK, a free download from Intuit. It provides a COM object interface or XML interface to all of the QuickBooks data. Additionally, if you need to do this over a WAN, you can use the QuickBooks Web Connector to talk to QuickBooks asynchronously over a WAN.
QuickBooks integration is not a trivial thing to accomplish. There are many gotchas. Your best friend will be the Intuit Developer Network forums.
You do not want to use QIF, QFX, or IIF exports. They are deprecated formats which can cause data corruption. Additional information about various methods of integrating with QuickBooks can be found on this integration wiki page and on this QuickBooks integration wiki.
查看 QuickBooks SDK。如果您想要更简单的使用方式，QODBC（具有写入功能），但不是免费的，对于 Access 来说可能会更容易使用。
Take a look at the QuickBooks SDK. If you want something simpler to work with, QODBC (with the write capabilities), while not free, will probably be simpler to work with for Access.
谷歌是你的朋友。 Quickbooks 具有一些原始的导入功能，但有许多小型产品可以满足您的需求。 这家伙似乎有一些相当不错的东西。本质上有几种不同的文本格式（QIF 和 OFX，如果没记错的话）用于 Quickbooks 导入，它们的问题是它们没有做太多的错误检查。还有一个 Quickbooks SDK，它允许您使用 COM (yum) 进行调用进行导入，并且可以进行完整的错误检查（它实际上调用了正在运行的 Quickbooks 版本），但对于您想要的东西来说可能有点过分了。
Google is your friend here. Quickbooks has some primitive import capabilities, but there are a number of small products that do what you need. This guy seems to have some pretty good stuff. Essentially there are a couple of different text formats (QIF and OFX if memory serves) that are used for Quickbooks import, the problem with them is they don't do much error checking. There is also a Quickbooks SDK which allows you to make calls using COM (yum) to import, and that does full error checking (it actually calls into a running version of Quickbooks), but is probably overkill for what you want.
查看 Quickbooks SDK 和 文档。该SDK有两个COM接口：QBFC和QBXML。使用 QBXML 的不同之处在于，您需要手动序列化和反序列化 XML，一旦掌握了 XML 的句柄，这并不难。我发现 QBXML 更方便，因为您可以选择包含您需要的请求和响应。
另外，如果您计划使用 Quickbooks SDK，请参阅在线参考是你最好的朋友。
Take a look at Quickbooks SDK and Documentation. The SDK has two COM interface: QBFC and QBXML. The difference in using QBXML, you need to serialize and deserialize XML manually which isn't hard once you get the handle of it. And I find QBXML much more convenient since you can choose to include requests and responses you need.
Also, if you plan to use Quickbooks SDK, the Online Reference is your best friend.
+1 易赛。我已经使用 qodbc 大约 10 年了，并且使用过 4 或 5 个不同版本的 Quickbook。 qodbc 利用类似于数据库的语法与公司文件进行交互。
与任何形式的正确数据库交互不同，在查询本身中尽可能少做工作，因为 qodbc 驱动程序可能需要 10 秒到 2 分钟来处理大约 1000 条记录的表中的十几条记录。可以导入 15 个订单（每行 5 行）的流程意味着与客户、项目、发票行、发票表进行交谈，并且可能需要 5 分钟。可悲的是，我在整理和理解数据的同时，常常沦落为基于批量导出构建MySql数据库。然后我回去尝试直接进行查询。
虽然在 Windows 中作为 ODBC 数据连接很棒，但要学会不信任工具链中的每个链接，并找出如何解决问题以证明某些方面完全正确和完全错误。我最近遇到的问题是 Win7 x64 计算机上的 QB11。当时的 php 堆栈值得怀疑并导致错误。并且请始终尝试执行错误检查，这在该环境中有点痛苦，但当“稍后出现问题”时变得至关重要。
此刻我正在研究 win7 的 php 堆栈，看看我是否可以再次信任它与 qodbc 和订单导入一起使用。 （从magento导出）
+1 to Yishai. I've been using qodbc for about 10 years now and 4 or 5 different versions of quickbooks. qodbc utilizes a database-like syntax to interact with the company file.
UNLIKE any form of proper database interaction, do as little work as possible in your query itself, as the qodbc driver can take 10 seconds to 2 minutes to handle a dozen records from a table of roughly 1000 records. A process that can import 15 orders with 5 lines each means talking to customer, item, invoiceline, invoice tables and can take 5 minutes. Sadly, I often am reduced to building a MySql database based on mass exports while I sort out and understand the data. THEN I go back and try to make queries directly.
While being an ODBC data connection in windows is great, learn to distrust each link in your toolchain and figure out how to troubleshoot problems to prove aspects positively correct as well as positively wrong. My most recent problem was with QB11 on Win7 x64 computer. The php stack at the time was suspect and was causing errors. And please always try to perform error checking, which is somewhat painful in that environment, but becomes crucial when "something breaks later".
This very minute I'm researching the php stack for win7 to see if I can again trust it for use with qodbc and order importing. (exporting from magento)