1. Home
  2. QuickBooks Discussions
  3. Java API for QODBC driver - Quickbooks

Java API for QODBC driver - Quickbooks

Hi,

I work for a small software company creating web based software for the moving industry

formatting link
As one of my projects, I have been tasked to create an accounts integration to Quickbooks (so financial information can be moved out of our software for accountancy purposes).

Our software is written in Java (J2EE) and I have decided after a fair bit of searching to write a few Java classes to interface with the QODBC (ODBC driver for QuickBooks).

After a bit of thought it hit me that if I extended it into a full blown and easy to use API encompassing the whole database layout, there may be a market out there for it.

Could anyone tell me if this would be the case, and if so tell me (honestly!) roughly how much you think it should cost.

Reply to
Jacqui
Loading thread data ...

formatting link

Reply to
L

If you wrote it in COBOL, I'd buy it in a hearbeat no matter the cost.

But Java?

For accounting?

Reply to
HeyBub

Firstly, I appreciate your comments on this subject. I am very interested in knowing why you would be so interested in the product being written in COBOL.

The reason I am writing it in Java is that the project I am working on (and many other companies I believe are working on) is a server side application which is accessed through a web browser. Java is one of the 2 top programming methods of writing software to be deployed in this fashion (the other is Microsoft's .NET).

The web front end allows the user to easily enter data specific to their area of expertise and the market the company they work for is in (in my case, the moving industry). The server-side system is then responsible for extracting relevant data and exporting it to the Quickbooks accountancy system. This currently includes Customers, Vendors, Purchase Invoices and Sales Invoices, but could be easily expanded (as I am suggesting) to include the whole database structure as available through the QODBC driver.

Reply to
Jacqui

They still use COBOL? Damn! Wonder if anyone needs an ex-COBOL instructor from the early eighties? I could always quit this keeping the accounts gig and have hubby hire a real trained bookkeeper for his business. How about Fortran? PL/I? IMS DB? Ramis... Pretty sure 360 BAL went out with the dinosaurs (I still remember when green card had absolutely nothing to do with immigration).

Gonna have Mr. Peabody start up the way-back machine.....

Reply to
L

You'd have to catch up. GUI, ODBC, OO, etc. Check, for example,

formatting link

Most "backroom" accounting activities for large organizations are still done in COBOL. Social Security checks, most paychecks, etc.

What other language provides for up to 30 digits of precision? Not "accuracy," that's easy. Precision.

Fortran is still very popular in the scientific community and I run into the occassional shop with PL/I. Don't have a clue as to the others you mentioned. DoD is big into ADA.

Reply to
HeyBub

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.