Access 2003 to Quickbooks
PW
been successful exporting Access data (2003 in our case) **TO**
Quickbooks?
My product only tracks some revenue but clients keep asking about
importing data from it into Quickbooks (NOT the reverse). I googled
and found basically nothing for years.
Thanks,
-paul w
Tony Toews [MVP]
Last time I read anythnig QB has an SDK or developers section on their website for
which you mgiht have to pay for.
Last time I did this, about ten years ago, this was ugly, ugly, ugly. The
documentation was sparse. The file format import unusual to say the least. There
were no useful error messages on the import data. And you could import the data
twice, which included invoice numbers that QB itself wouldn't let you you enter in
twice.
Hopefully they've spent a week or so cleaning all that up since.
Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/
Karl
Data can be imported into QuickBooks using either IIF files or XML
files. IIF files are text files in QuickBooks IIF format which is
somewhat documented in QuickBooks help. For XML you need the
QuickBooks Software Development Kit (SDK). See www.developer.intuit.com
for information on the SDK. Access can be used to create IIF files.
(you click File>Utilities>Import... in QuickBooks to import them.
Access can also be used with the SDK.
PW
<tto...@telusplanet.net> wrote:
>PW <emailad...@ifIremember.com> wrote:
>
>>I don't even know why I am asking again but surely someone here has
>>been successful exporting Access data (2003 in our case) **TO**
>>Quickbooks?
>>
>>My product only tracks some revenue but clients keep asking about
>>importing data from it into Quickbooks (NOT the reverse). I googled
>>and found basically nothing for years.
>
>Last time I read anythnig QB has an SDK or developers section on their website for
>which you mgiht have to pay for.
>
>Last time I did this, about ten years ago, this was ugly, ugly, ugly. The
>documentation was sparse. The file format import unusual to say the least. There
>were no useful error messages on the import data. And you could import the data
>twice, which included invoice numbers that QB itself wouldn't let you you enter in
>twice.
>
>Hopefully they've spent a week or so cleaning all that up since.
>
>Tony
Thanks Tony. That is what I thought. And I am guessing that I am
also going to have to worry about all the various versions of
Quickbooks/Quicken.
-paulw
PW
wrote:
Thanks Karl. I am thinking the import to QB would have to be automatic
from my Access application.
-paulw
David W. Fenton
news:nbqbi55pg0rq4t4vb...@4ax.com:
> Last time I read anythnig QB has an SDK or developers section on
> their website for which you mgiht have to pay for.
Last time I looked into it (within the last year or two), the SDK
was free to download. From what I got skimming the docs, it seemed
like access to the data was very inefficient, like Outlook from
Access, i.e., you have to walk collections a lot. The access to the
data is not like you get with a database.
I don't know what happened to the ODBC drivers. Those may have been
3rd-party.
--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
David W. Fenton
news:0d3di55l6t3otgp5t...@4ax.com:
> I am
> also going to have to worry about all the various versions of
> Quickbooks/Quicken.
QB and Quicken are completely different animals. The QB SDK won't
give you any help with Quicken. So far as I know, the only
interoperability with Qicken is through the QIF file import/export
format.
The last time I gave this serious consideration, I concluded that
batching updates in QIF files was going to be easier than automating
QB. This is all much easier if you're pulling data out of QB for use
in Access and not needing to push any data into QB.
David W. Fenton
news:8i3di5lf9s2u9sc15...@4ax.com:
> I am thinking the import to QB would have to be automatic
> from my Access application.
It may be that you can automate QB to do the import, but I don't
know.
PW
<XXXu...@dfenton.com.invalid> wrote:
>"Tony Toews [MVP]" <tto...@telusplanet.net> wrote in
>news:nbqbi55pg0rq4t4vb...@4ax.com:
>
>> Last time I read anythnig QB has an SDK or developers section on
>> their website for which you mgiht have to pay for.
>
>Last time I looked into it (within the last year or two), the SDK
>was free to download. From what I got skimming the docs, it seemed
>like access to the data was very inefficient, like Outlook from
>Access, i.e., you have to walk collections a lot. The access to the
>data is not like you get with a database.
>
>I don't know what happened to the ODBC drivers. Those may have been
>3rd-party.
Thanks David. Nice to hear from you.
We presently have a report that sorts things into QB classes and it
literally takes someone 5 minutes to manually enter the data (we
essentially just track income) into their version of Quickbooks.
But that is the number one question we get asked (if our product is
"compatible" with Quickbooks). I am not sure how our "competitors"
manage to do it but it's just my wife and I.
-paul
mike
Karl
> On Mon, 14 Dec 2009 07:09:15 -0800 (PST), Karl <karl3...@gmail.com>
For automatic imports use the SDK. It can "push" data into QB, even if
QB isn't running.