|
Buy Support
Incidents |
|
If you can't find your answer
in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us
private or confidential information: |
|
Click Here
|
If you can't
login and post questions or you are having trouble viewing forum posts:
Click Here
|
Callback
Support |
|
If you live in USA, UK, Canada, Australia or New
Zealand, you can leave us details on your question and request us to call you back and discuss
them with you personally (charges apply). |
|
Click Here
|
Buy Support
Incidents |
|
If you can't find your answer
in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us
private or confidential information: |
|
Click Here
|
|
| Integration of QODBC & "ODBC Socket Server" Open Source Web Servers |
| Author |
Message |
| Tom |
 |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2006-02-22 09:51:45 |
After lengthy searching on your site, and on the web in general, I found a nice alternative to link the QODBC driver to an open source web server, in this case Apache2/php running on Novell Netware. The solution I found works wonderfully, and though I'm running in on netware, it is actually platform and language independant.
Here's what I have:
A machine running Windows 2000 professional, with a full install of Quickbooks, and the QODBC driver. Along with that, there is a component called "ODBC Socket Server" a open source GPL software package I found on the internet that makes Local ODBC machine sources available any computer on your network through generic XML.
The ODBC Socket server sends and receives XML pages from any device and translates it to a local ODBC call which your qodbc driver then sends to quickbooks, performs the query, and returns the data to the odbc socket server, which then translates the results back into XML, and sends the response to the requesting machine.
Once the response has been received, it can be parsed in any language that has an XML DOM compliant parser, and the initial row in the response includes the fieldnames.
|
|
|
|
|