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 : Can multiple Access .MDEs connect to QODBC simultaneously?Search Forum

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

 New Topic 
 
 Post Reply 
[1]  
 Can multiple Access .MDEs connect to QODBC simultaneously? 
 Author   Message 
  David 
  
 Group: Members 
 Posts: 16 
 Joined: 2007-08-09 
 Profile
 Posted : 2007-10-18 03:02:41
I've written an MS Access application I'm deploying to several employees who need simultaneous access to QB Data through the QODBC connector. It works great on my development machine, but more than 1 client and it appears security rights are revoked and I get an 'ODBC Call Failed' error. I must then re-login as the Administrator, re-grant access rights to re-establish the connection. The Access .mde is copied on the the individual client machines, so I'm assuming the are functioning as unique 'programs' to QB security. Why won't it remember the settings and allow multiple logons? Will your Server version allow this functionality?

Running Quickbooks 7.0 Enterprise w/ Built-in QODBC and  Access 2003. 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2007-10-18 08:10:15
When your application is copied to another workstation it only has the QODBC connection parameters. When any QODBC application connects to a copy of QuickBooks for the first time, Intuit's security settings require the connection to be authorised by the QuickBooks user. This also happens with new company files. 

  Top 
  David 
  
 Group: Members 
 Posts: 16 
 Joined: 2007-08-09 
 Profile
 Posted : 2007-10-18 22:39:35
When Client 1 connects, I approve it's security connection in Quickbooks, logout and change to another Quickbooks user. Reconnect and everything works well. When Client 2 connects, I approve it's security connection in Quickbooks, logout and change to another Quickbooks user. Still works correctly. When I return to Client 1, I find the connection broken and receive nothing but "ODBC Call Failed Errors". I have to relogin as Admin, re-approve it's security setting, then it works again, while Client 2 just lost it's connection. Same cycle. Any ideas? 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2007-10-19 08:17:52
Sorry, is this on different workstations? What you write almost sounds like Windows Terminal Services or Citrix here. The QODBC connection on a computer can only be setup to use one QuickBooks account. See: What is error: 3260 (“Insufficient permission level to perform this action”)? for more info. 

  Top 
  David 
  
 Group: Members 
 Posts: 16 
 Joined: 2007-08-09 
 Profile
 Posted : 2007-10-19 22:06:33
Hm.. It probably is an account issue. I'm not using Terminal Services nor Citrix. Client 1 is one machine running Quickbooks and my Access Application. Client 2 is a second machine running Quickbooks and my Access Application. Both access the SAME Quickbooks File, located on a third machine - the server. I've tried configuring the "login as field" in QB to the SAME user account and to SEPARATE accounts. It still allows only one client to have access at a time, and when I change systems, I must re-approve the application in Quickbooks, UNLESS one client is the Admin. The Admin always has access, even if another account is connected and active. I've also tried changing the names of each of the .MDEs, and it still doesn't work properly. 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2007-10-20 09:20:30

Actually it's a certificate problem. To setup up multiple users they either have to have seperate certificates for each QuickBooks user or use the QODBC Remote Connector so all QODBC - MS Access connections use the Admin account instead.

If you remove all the "FLEXquarters QODBC" integrated applications and connect your MS Access application on Client 1 as a user, you can then setup and use Client 2 as another user at the same time using VB Demo, but not as another MS Access application using the same certificate. Meaning different applications, different QuickBooks user accounts, different certificate.

If you use the QODBC Remote Connector, then on Client 1 (Admin user) the iBiz Remote Connector is run along with QuickBooks and all other users need to use the QODBC Remote Connector to connect to the one copy of QuickBooks on Client 1 via its TCP/IP address. The QODBC Remote Connector allows multiple simultaneous connections to the Host iBiz Remote Connector.

For further information on using the QODBC Remote Connector and the iBiz Remote Connector see: I do not want to install QuickBooks on every machine. How do I setup QODBC Remote? 

 

  Top 
  David 
  
 Group: Members 
 Posts: 16 
 Joined: 2007-08-09 
 Profile
 Posted : 2007-10-23 07:08:55
Since I'm currently using the Built-In QODBC version that is included with QB 7.0 Enterprise, I realize I'll have to purchase the 'full' version to use the iBiz remote connector. How many user licenses will I be required to get? It looks like I can run the 'connector' on the Server with QB, and use the 'client' on each machine with my application connecting through iBiz. Do ALL users require the Full Version or just the Server? 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2007-10-23 08:16:50
The remote connector can be configured using the bundled QODBC Enterprise Edition, just download the full installer, see: How can I get the latest version of QODBC?  

  Top 
  David 
  
 Group: Members 
 Posts: 16 
 Joined: 2007-08-09 
 Profile
 Posted : 2007-10-23 23:00:55
I have downloaded and installed the  most recent full version on both my server and workstation. The server says I have 30 days to evaluate the driver, while my workstation does not. QB 7.0 Enterprise is installed on both and working just fine. I can create a connection on the server, run the iBiz connector and VBDemo access the data properly. When I switch to my workstation, I copy the settings ( I even tried copying a fileDSN) and receive the "This Version is for Enterprise Only, please download...." error. Any thoughts? 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2007-10-24 10:26:24
You need to update the copy of QODBC on the workstation to v8.00.00.237 (or higher) see: How can I get the latest version of QODBC?  

  Top 
  David 
  
 Group: Members 
 Posts: 16 
 Joined: 2007-08-09 
 Profile
 Posted : 2007-10-24 22:55:14
The latest version is installed on both machines. 8.00.00.237. Still getting the same error: "Only Licensed for Enterprise..."  I've uninstalled and re-installed with no change. Anymore ideas? 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2007-10-25 12:27:14
What does the "About" tab is the QODBC Setup Screen say is running on both the server and workstation? What are the license types? 

  Top 
  David 
  
 Group: Members 
 Posts: 16 
 Joined: 2007-08-09 
 Profile
 Posted : 2007-10-25 22:16:27
O.K., Tom, this is a problem.
The SERVER reads "Evaulation QODBC Server Edition 2008, ver 8.00.00.237", Expires in 28 days.
The WORKSTATION reads "QODBC Desktop Edition Only 2007, ver 8.00.00.237" No Expiration.

I installed the Trial on a 2nd Workstation configured it the same as my 1st workstation (or so I thought). This 2nd Workstation has QB Enterprise 7.0 installed with QODBC 8.00.00.37 installed over top. Here is what the 'about' says:
WORKSTATION2 - "Evaluation QODBC Server Edition 2008, ver 8.00.00.237", Expires in 28 days.

It does NOT connect to the SERVER, but it DOES connect to my workstation when I run the 'connector.'

How can I get all these on the same version/type? 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2007-10-26 09:09:43

It's normal for the full version of QODBC to say it's in evaluation mode for the first 30 days of use. If you are runnning QuickBooks Enterprise on the workstation, then QODBC will detect that and continue to run in QODBC Enterprise Edition (read-only) mode after the evaluation has expired.

The iBiz Remote Connector is only run on the server and your workstation QODBC Remote Connector setup must point to the IP of your server.

 

  Top 
  David 
  
 Group: Members 
 Posts: 16 
 Joined: 2007-08-09 
 Profile
 Posted : 2007-10-30 02:12:31
I have it working between another Workstation and the server now. Thanks for all your help. I do have a small issue with my development workstation, in that I installed the QReports Builder Demo a while back. After uninstalling it, the QReports still showed up in the 'About' section, but not all the time. I recently did a Custom Uninstall or the QODBC driver selecting to remove all Registry Entries. Now, the 'about' box reads, "QODBC Desktop ReadOnly Desktop, Version 8.00.00.237, OPEN LICENSE FAILED." After seeing this error, I have NOT reinstalled. Should I? Or do you have a way of removing/restoring the Reg Entries? Thanks. 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2007-10-30 07:48:31
Please rename the I9K4UQLW.ocx QODBC registration license file to I9K4UQLW.bad in your Windows System32 folder and re-run the install file for QODBC again. 

  Top 
 New Topic 
 
 Post Reply 
[1]  

Jump to