That's not at all what I read on QB's website. They have SDKs for you
to download, saying they no longer support import/export of data
files, and you program an interface using program languages such as
.Net and C++. And that the days of the .IIF import files are over
Karen
-----Original Message-----
From: James W. Kim, CPA, MBA <[email protected]>
To: rbase-l <[email protected]>
Sent: Tue, May 9, 2017 2:28 pm
Subject: Re: [RBASE-L] - Quickbooks
I am not sure if following info is what you are looking for.
Nevertheless, these days, it's relatively easy to import/export data
with Quickbooks. It can import Excel or csv file easily. Also many
banks provide transaction details on .qbo files just for importing
into Quickbooks. The .qbo appears to be a type of XML file. Looking
at the content of .qbo files, R:Base can be easily programmed to
produce .qbo files from data table.
--
James
On 5/9/2017 2:41 PM, karentellef via RBASE-L wrote:
Great question
Karen
-----Original Message-----
From: Bruce Chitiea <[email protected]>
<mailto:[email protected]>
To: rbase-l <[email protected]>
<mailto:[email protected]>
Sent: Tue, May 9, 2017 11:54 am
Subject: Re[2]: [RBASE-L] - Quickbooks
Ok then, looking forward.
Is anyone aware of - or had any direct experience with - ANY
accounting system in QuickBooks' market segment (Peachtree,
perhaps) which hosts dead-bang, SQL-compliant import/export
capabilities; with or without resort to third-party "translators"?
Bruce Chitiea
SafeSectors, Inc.
909.238.9012 Mobile
------ Original Message ------
Sent: 5/9/2017 8:47:08 AM
Subject: Re: [RBASE-L] - Quickbooks
From: "Bill Downall" <[email protected] <mailto:[email protected]>>
To: [email protected] <mailto:[email protected]>
Cc:
I've built a bridge between R:BASE and QB through a 3rd party
product called Transaction Pro Importer out of Bay State
Consulting. It's been working well for years, but Karen is right:
when QB gets upgraded or moved from desktop to cloud, the TPI
product may have to change and the R:BASE end reworked, too.
That company's experience with trying to move from QB Desktop to
QB Online was a disaster, as others have described. (Would have
had to archive/abandon historical details, and it still took over
24 hours to convert in testing.) I've also seen a non-profit I
have worked with abandon efforts to improve their QB by moving it
to QB Online.
Frank's story -- a company spending 6 figures to learn that
moving to XXX was not an improvement in the end -- is one many
people have shared and heard over and over again when R:BASE
developers got together.
On Tue, May 9, 2017 at 11:31 AM, karentellef via RBASE-L
<[email protected] <mailto:[email protected]>> wrote:
Thanks for the two cents. Just confirms everything I've
heard that QB does _not_ want to talk to other programs. The
vertical market app they're looking at apparently has a
separate add-on program you can buy to make the transfer, but
who knows what version of QB it interfaces with. Gonna share
your post (but not your name) with the company.
Karen
-----Original Message-----
From: Frank Massimo <[email protected]
<mailto:[email protected]>>
To: rbase-l <[email protected]
<mailto:[email protected]>>
Sent: Tue, May 9, 2017 10:21 am
Subject: Re: [RBASE-L] - Quickbooks
Karen,
One of my clients has been using R:Base from DOS through
Enterprise 10 (nearly 20 years). Their accountant felt that
the AR portion of the R:Base application should be handled
through Quickbooks (Enterprise Ver 14). They have been using
QB as a check writer for years. I made a number of arguments
against it, as they produce 1000-1300 invoices per day and the
well-honed, specialized R:Base programs developed to create,
track and process the ultimate payment of 1000-1300 invoices a
day was in place and working. The only thing that was missing
was integration of AR numbers for general ledger purposes in
Quickbooks, which I pointed out could be produced easily on
demand when the necessary reports were required. The
accountant prevailed and the debacle began. I wrote the
necessary programs to provide overnight data which had to be
fed to QB via Transaction Pro because the QB process of
importing the data was too slow. On the AR side, all of the
specialized functionality of the custom R:Base programs was
lost so the AR staff had to learn (the hard way) that QB had
pretty screens and some neat features but it took them twice
as long to post invoices, not to mention the dozens of other
glitches the import process encountered, the difficulty of
handling incoming EDI payments, and all of the other oddities
that R:Base let's you code around. That's the short version,
but bottom line, I am now busily migrating the AR system back
to R:Base.
Just my two cents. Cost them six figures to come to the same
conclusion, though.
Frank Massimo
Tri-State Logistics, Inc.
------------------------------------------------------------------------
*From:* karentellef via RBASE-L <[email protected]
<mailto:[email protected]>>
*Sent:* Thursday, May 4, 2017 1:17 PM
*To:* [email protected] <mailto:[email protected]>
*Subject:* [RBASE-L] - Quickbooks
It's been decades since I've had to deal with Quickbooks, and
it wasn't exactly a joy back then...
Someone just asked me about sending stuff from RBase into
Quickbooks (they do not own QB yet, so it would be a new
version of the software).
Has anyone here used a new version of QB and let me know if
it's easier nowadays to send data to QB? For example, what
kind of formats does it accept as an import? Any gotchas? We'd
probably be sending over lists of "members" (name, address,
etc), and different kinds of revenues received (member fees,
special fees, event fees)
Thanks for any insight!
Karen
--
You received this message because you are subscribed to the
Google Groups "RBASE-L" group.
To unsubscribe from this group and stop receiving emails from
it, send an email to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout
<https://groups.google.com/d/optout>.
--
You received this message because you are subscribed to the
Google Groups "RBASE-L" group.
To unsubscribe from this group and stop receiving emails from
it, send an email to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout
<https://groups.google.com/d/optout>.
--
You received this message because you are subscribed to the
Google Groups "RBASE-L" group.
To unsubscribe from this group and stop receiving emails from
it, send an email to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout
<https://groups.google.com/d/optout>.
--
You received this message because you are subscribed to the Google
Groups "RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.