yes, I have written an api that allows you to read and write information with Quickbooks.
-Nathan
On 5/21/2012 11:05 AM, Kevin Christensen wrote:
Has anyone out there written a D3 / Quickbooks API interface? I'd
certainly not want to reinvent the wheel.
Thanks,
Kevin Christensen
--
You received this message because you are subscribed to
the "Pick and MultiValue Databases" group.
To post, email to: mvd...@googlegroups.com
To unsubscribe, email to: mvdbms+unsubscribe@googlegroups.com
For more options, visit http://groups.google.com/group/mvdbms
--
Nathan Rector
International Spectrum, Inc
http://www.intl-spectrum.com
Phone: 720-259-1356
Fax: 603-250-0664
Twitter: http://twitter.com/intlspectrum
Facebook: http://intl-spectrum.com/facebook
--
You received this message because you are subscribed to
the "Pick and MultiValue Databases" group.
To post, email to: mvd...@googlegroups.com
To unsubscribe, email to: mvdbms+unsubscribe@googlegroups.com
Wil, Quickbooks has a much larger user base than MV. Discretionary posturing is advised. :)
I spoke with a client, MV ERP VAR, about this once before Nathan went production with his software. The discussion went something like this:
me: how many of your clients use Quickbooks?
client: all of them.
me: don't you see any value in sharing data between your application and theirs?
client: no.
Just from the above, I've often wondered why that VAR did not internalize Why "all" of his clients were using Quickbooks when his application included an Enterprise-scale accounting package. And how could he not think about all of the double entry being done by his clients between their two systems?
From this and many other depressing discussions like it, I've found over the years that the issue is rarely with end-user business requirements. The problem is usually the ability of VARs to see beyond the capabilities of their own application, and to accept that end-users may want to do something that's not in the Pick box that's provided to them. For decades we've been stuck with this mantra that Pick is an Operating System, that it has a word processor (JET) and spreadsheets (UltiCalc, etc) - why would anyone look beyond that? Um … duh. Because there is other specialty software out there that does specific jobs much better. So the decision should then be - if that's what people are going to use, how do I integrate with it in the name of survival. Most VARs simply do not integrate with the outside world, so our industry has shrunk over the years as end-users continue to look elsewhere for their integrated solutions. The VARs who move with the times have continued to prosper.
This is yet another answer to "why Pick didn't take off as it should". The answer includes lack of vision beyond the 80x24 screen (amongst some but of course not all developers), and posturing ("why would anyone need that other stuff when they have what I provide?"). The fact is that end-users do need more. There ARE more than eight clients out there using Quickbooks. People need to get their heads out of the sand, and like Nathan, respond to the needs of the real world rather than pretending it doesn't exist.
T
From this and many other depressing discussions like it, I've found over the years that the issue is rarely with end-user business requirements. The problem is usually the ability of VARs to see beyond the capabilities of their own application, and to accept that end-users may want to do something that's not in the Pick box that's provided to them. For decades we've been stuck with this mantra that Pick is an Operating System, that it has a word processor (JET) and spreadsheets (UltiCalc, etc) - why would anyone look beyond that? Um … duh. Because there is other specialty software out there that does specific jobs much better. So the decision should then be - if that's what people are going to use, how do I integrate with it in the name of survival. Most VARs simply do not integrate with the outside world, so our industry has shrunk over the years as end-users continue to look elsewhere for their integrated solutions. The VARs who move with the times have continued to prosper.
T
Huh?
Dude, the question from the OP was " Has anyone out there written a D3 / Quickbooks API interface?" I interpret the word "sockets" in the subject as a guess at How the interface would be done but that's irrelevant. You solve the problem using the best tools. I'm sure the OP doesn't care how the problem is solved And the technical matter of how it's solved is independent of the API and subject to change anyway. This is all a red herring.
When you buy goods at the store you don't are about what kind of truck brought it there. The question is about the goods. I was commenting on how VARs believe their "goods" are adequate while their clients are busy shopping in other stores.
D3 Sockets is a topic that was discussed ad-nauseum and closed a decade ago. Sure we can do sockets with D3 and other platforms. But we generally don't want to or need to. If you're interested in sockets, I suggest you have a look at the CDP archives, maybe PickWiki, and then if you want to talk about sockets rather than Quickbooks, open a new thread and let's see who jumps in.
"is this type of INTERFACE saleable?"
From: Wjhonson
You misunderstand what I'm stating.
The OP wanted a D3 Sockets / Quickbooks Interface
Not just a Quickbooks interface.
The marketing universe for a D3 Sockets / Quickbooks Interface is eight clients :)
That was my point.
…[snip]
Bruce, just for reference, Drexel has come to use the exact same toolkits as I do. There are at least two kinds of "VAR". There are those who completely develop their own business management applications internally. And there are those who sell toolkits and/or provide development services for other application developers. Drexel is both - they have business management apps and they provide tools and services. I do not have a business management app, but I do provide development tools and services.
I only clarify this because I was talking specifically about those who have apps but they do not sell tools to other developers. These folks are very focused on their apps and often aren't connecting dots between end-user requirements and tools available to satisfy them.
Again, I don't mean to generalize here. If someone does not fit that description then I'm not talking about them and they shouldn't feel like a comment is being made about them. But for anyone who does fit the description … perhaps it's time to consider a new round of discussion with end-users.
BTW, I also applaud Drexel as being a successful, stand-up business in this industry. Yes, Mark works for Drew, and both of them are tops at what they do.
Best,
T