Member Login

Username
Password
Forget Password
New Sign Up
Search Forum

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

Forum : Unable to exec query through SQL Server 2005 Management Studio as a linked serverSearch Forum

Forum Home > QODBC - ODBC Driver for QuickBooks > QODBC v6 Forum

 New Topic 
 
 Post Reply 
[1]  
 Unable to exec query through SQL Server 2005 Management Studio as a linked server 
 Author   Message 
  Tom 
  
 Group: Members 
 Posts: 5 
 Joined: 2006-08-01 
 Profile
 Posted : 2006-11-03 12:49:52

I have followed the instructions for running QODBC with MS SQL Server 2005 Linked Tables many times. I am unable to make this work. While running one of the example queries (SELECT * FROM OPENQUERY(QODBC, 'SELECT * FROM Host')) through Management Studio I get as far as "Executing query..." and I hear the windows default beep sound seconds later. 

We're running QODBC Server Edition 2007 Version 6.00.00.176

DCOM Servers setting is enabled.

Flexquaters QODBC is setup through QB to Allow this application to access the company file, allow this application to login automatically, login as admin, and allow this application access to personal data. 

I am able to use the VB Demo app successfully. 

I am able to run queries through ASP using the QODBC system DNS successfully. 

The ASP DCOM Access Test Page lists all success statues. 

I have changed the MSDASQL properties as indicated in the instructions. 

I have run the Test DCOM Script and all objects return "Successfully Created".

I have tried some of the troubleshooting tips from http://www.qodbc.com.au/QODBCwebserver.asp 

 

I am able to execute queries through ASP using the linked server using the SQL Server ODBC driver with the sample queries (SELECT * FROM OPENQUERY(QODBC, 'SELECT ListID, Name FROM Employee'). However this does not work through SQL Server 2005 Management Studio. I do not understand the difference. 

 

I am willing to email my detail trace log. QODBC Messages and SDK Messages do not seem to have any interesting log entries.

 

 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2006-11-03 18:10:51

Try running the Query with QuickBooks and the company file open (or if that's what you were doing ... try the other way around). But OPENQUERY queries like this should run if the MSDASQL (Microsoft OLE DB Provider for ODBC Drivers) provider is setup correctly, but you can also try:

SELECT ListID, Name FROM QODBC...Customer

 

  Top 
  Tom 
  
 Group: Members 
 Posts: 5 
 Joined: 2006-08-01 
 Profile
 Posted : 2006-11-04 04:04:16

Yes, I have tried with the QuickBooks company file open with the administrator logged in and with QODBC configured to automatically launch QuickBooks as a hidden process and login as admin. In my case I would prefer the auto login but yes I have tried both.

 

I also tired both formats of the sample queries (OPENQUERY and QODBC…) with the same results.

SELECT * FROM OPENQUERY(QODBC, 'SELECT * FROM Host')
SELECT * FROM QODBC...HOST

I am using SQL Server 2005 Express on Win XP SP2. It should be worth noting that SQL 2005 Express does not have the property menu item on the Link Server providers so I was unable to configure this through the UI as indicated in the directions. However I did script this action from another SQL Server and I believe I have achieved the same results, but I do not know anyway to verify this.

USE [master]
GO
EXEC master.dbo.sp_MSset_oledb_prop N'MSDASQL', N'DynamicParameters', 1
GO
EXEC master.dbo.sp_MSset_oledb_prop N'MSDASQL', N'IndexAsAccessPath', 1
GO
EXEC master.dbo.sp_MSset_oledb_prop N'MSDASQL', N'LevelZeroOnly', 1
GO
EXEC master.dbo.sp_MSset_oledb_prop N'MSDASQL', N'NestedQueries', 1
GO
EXEC master.dbo.sp_MSset_oledb_prop N'MSDASQL', N'NonTransactedUpdates', 1
GO

 

  Top 
  Tom 
  
 Group: Members 
 Posts: 5 
 Joined: 2006-08-01 
 Profile
 Posted : 2006-11-04 08:23:07

I've been playing with this most of the day and I’ve found a query that works through SQL Server 2005 Express on the host machine.

SELECT ListID, Name, CompanyName FROM QODBC...Vendor

Interestingly enough when I execute this query from a different machine connecting remotely to SQL Server I get the same indefinite “Executing query…” and default beep sound from the host machine that I get when trying other queries.

At least to me there does not seem to be any reason as to why some work and most do not. I think the default beep is indicating a QODBC error since it occurs on the host machine, but I can’t find anything meaningful in the logs. Have any more ideas?

 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2006-11-04 11:22:51

Normally all the QODBC queries are run on the host system using the local database. By the sounds of things, the Studio is trying to run QODBC locally on the machine connecting remotely to SQL Server?

 

  Top 
  Tom 
  
 Group: Members 
 Posts: 5 
 Joined: 2006-08-01 
 Profile
 Posted : 2006-11-04 11:43:06

I have other computers with the client tools installed (Management Studio). QODBC and SQL Server 2005 Express are on the same system.

I can only get one query to work when trying everything locally. Everything else I try fails. Why?

 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2006-11-04 17:19:17
My understanding is that you need envoke a stored procedure on the host from the remote clients. BTW: If you want to call QODBC you should call QODBC directly. Most users move data from QuickBooks to their SQL Server database and have their clients call the SQL database directly. The host is then used as an interface to update records to and from QuickBooks. 

  Top 
 New Topic 
 
 Post Reply 
[1]  

Jump to