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
|
|
Driver error - Keyword not supported: 'driver'? |
Author |
Message |
Rob |
|
Group | : Members |
Posts | : 4 |
Joined | : 2006-05-02 |
|
Profile |
|
Posted : 2006-05-09 07:19:26 |
Hello,
We are getting the following error when trying to access the QODBC driver:
Keyword not supported: 'driver'.
using the example connection string:
Driver={QODBC Driver for QuickBooks};OptimizerDBFolder=C:\Program Files\QODBC Driver for QuickBooks\Optimizer;IBizRemotePWD=######;IBizRemoteConnect=Yes;IBizRemoteURL=http://aaabbb.com:2080; IBizRemoteConnTimeOut=120;IBizRemotePromptForPWD=No;IBizRemoteForce2002_2003=Yes; OpenMode=M;DFQ=C:\QBOOKS\DW.QBW;OLE DB Service=-2
(url and password modified to protect security)
We are trying to open the remote driver on our server, any suggestions on where to start? We are running Windows 2000 and IID on .net 1.1 (VB)
Thanks in advance,
Rob |
|
|
|
Tom |
|
Group | : Administrator |
Posts | : 5510 |
Joined | : 2006-02-17 |
|
Profile |
|
Posted : 2006-05-09 08:37:41 |
Your missing the start of the statement. Here's a full example for context:
Visual Basic 6 Example Requires project reference to Microsoft ActiveX Data Objects 2.x Library
'***************************************** Dim oConnection As ADODB.Connection Dim oRecordset As ADODB.Recordset Dim sMsg As String Dim sConnectString As String Dim sSQL As String sConnectString = "Driver={QODBC Driver for QuickBooks};DFQ=C:\Program Files\QODBC Driver for QuickBooks\sample04.qbw;OpenMode=M;OLE DB Services=-2;" sSQL = "SELECT Name FROM Employee" Set oConnection = New ADODB.Connection Set oRecordset = New ADODB.Recordset oConnection.Open sConnectString oRecordset.Open sSQL, oConnection, adOpenStatic, adLockOptimistic sMsg = "**********************" & Chr(10) Do While (Not oRecordset.EOF) sMsg = sMsg & oRecordset.Fields("Name") & Chr(10) oRecordset.MoveNext Loop sMsg = sMsg & "**********************" & Chr(10) MsgBox sMsg oRecordset.Close Set oRecordset = Nothing oConnection.Close Set oConnection = Nothing '*****************************************
See: How do I build a connection string with all the available QODBC parameters? for more. |
|
|
|
Rob |
|
Group | : Members |
Posts | : 4 |
Joined | : 2006-05-02 |
|
Profile |
|
Posted : 2006-05-11 11:52:17 |
Thanks, another question. I am accessing quickbooks from our web server, and quickbooks is running on our department server. The connection works great from access, I can query tables without issue. When I try from asp.net, using the following string, the system just hangs:
Driver={QODBC Driver for QuickBooks};DFQ=C:\Program Files\QODBC Driver for QuickBooks\sample04.qbw;OpenMode=M;OLE DB Services=-2;
Since the config is loaded on the web server, there is no quickbooks file on the local server. So to that end:
Is the DFQ line set to the location of the file on the remote server? Any reason why connecting to an ODBC source in .NET would hang?
I can connect to other ODBC clients, so I am thinking this is local to QODBC.
Thanks! |
|
|
|
Tom |
|
Group | : Administrator |
Posts | : 5510 |
Joined | : 2006-02-17 |
|
Profile |
|
Posted : 2006-05-11 12:11:31 |
QODBC needs to talk to QuickBooks, it doesn't talk to the company file directly. The DFQ reference is used to tell QuickBooks which company file we wish to talk to. By the sound of things, QuickBooks isn't on your Web Server, so you need to use the QODBC Remote Connector connection string to send the request to your Department Server. The DFQ line is set to the local location of the file on your Department Server.
A .NET application running as a Windows Service (ASP.NET) connection requires either a QODBC Server Edition and the DCOM Servers or a QODBC Remore Connector. |
|
|
|
Rob |
|
Group | : Members |
Posts | : 4 |
Joined | : 2006-05-02 |
|
Profile |
|
Posted : 2006-05-11 16:05:54 |
Thanks,
Any idea based on my connection string why things would be locking up in .net and not in access?
-Rob |
|
|
|
Rob |
|
Group | : Members |
Posts | : 4 |
Joined | : 2006-05-02 |
|
Profile |
|
Posted : 2006-05-11 16:23:03 |
One other thing that might help. I tried to turn on logging from the qodbc driver level, and then thought I could see the connection string access uses and just copy that, or see the error that is happening from the .net app, but neither event is captured in the log, only failed auth attempts from days ago.
Should the trace be showing all commands going through the driver? Is there a better to debug this issue?
Thanks!
Rob |
|
|
|
Tom |
|
Group | : Administrator |
Posts | : 5510 |
Joined | : 2006-02-17 |
|
Profile |
|
Posted : 2006-05-11 17:36:53 |
The QODBC trace log will only show connections that fail other than Windows security issues in the first place. Using the Windows Explorer Security tab, give read and write rights to the QuickBooks application folder (normally C:\Program Files\QODBC Driver for QuickBooks\) to the Anonymous web user IUSR_machinename, ASPNET user and INTERACTIVE. This should allow for the creation and update of QODBC trace and message logs by your .NET application. |
|
|
|
|