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 : QB thinks 'user' is still logged in after closing MS Access applicationSearch Forum

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

 New Topic 
 
 Post Reply 
[1]  
 QB thinks 'user' is still logged in after closing MS Access application 
 Author   Message 
  Kelley 
  
 Group: Members 
 Posts: 7 
 Joined: 2007-10-10 
 Profile
 Posted : 2007-10-10 23:53:52

I  have written a MS Access front end application that reads 3 QB tables (Customer, PO heaers, and PO lines) using QODBC.  My problem is that I close the MS Access front end, and if I go to close QB I am not able to do that.  QB gives a warning "Already open  exclusively by another user".  It seems that QODBC is still "logged into" QB.  If I wait 15 minutes, I am able to close QB okay.

Is there any way to get QODBC to "log out" of QB when I close my MS Access front end?

Kelley

 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2007-10-11 07:55:20
Your company file and front end connection must be in multi-user mode. Normally when MS Access is closed, the connection is also closed. The only reason I can think off of why you have to wait 10 or 15 minutes would be if your front end is called via a Windows Service like Task Scheduler. Applications that run as a service, or are called by a service, take 10 or 15 minutes to be really released by the Windows O/S once the task is terminated. 

  Top 
 New Topic 
 
 Post Reply 
[1]  

Jump to