|
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
|
|
| Multi-user mode prevents Quickbooks shutdown |
| Author |
Message |
|
|
| Posted : 2008-07-24 04:31:27 |
I have a customer who is using QODBC on a machine with a 5-user installation of Quickbooks Enterprise Solutions version 8.0. When my app is shut down, Quickbooks still refuses to close, giving the error that an active session is still connected to Quickbooks. I have verified that all tasks are shut down, so Quickbooks should close. However, the only way to get it to close is to forcibly end the task via task manager. How do I resolve this problem? |
|
|
|
| Tom |
 |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2008-07-24 08:18:38 |
|
|
|
|
|
| Posted : 2008-07-24 08:54:24 |
| My application uses ADO from within Access to query Quickbooks via the QODBC driver. I have verified that everything closes down properly, yet I continue to receive this message everytime the customer uses my app. It's not going to be acceptable to them to have to close Quickbooks from the Task Manager from now on. What else can I try? Is this a bug in the driver? |
|
|
|
| Tom |
| |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2008-07-24 09:25:08 |
| Once you close Quickbooks from the Task Manager you will need to restart Windows to actually completely remove the dll in memory. |
|
|
|
|
|
| Posted : 2008-07-24 09:47:39 |
Tried that too ... the problem re-appeared as soon as I launched my Access DB and ran the query. Nothing fancy - just a simple ADO connection via the DSN I created using the QODBC DSN tool, and then creation of a Recordset object using standard SQL. Close the DB, and try to close QB, and error appears. Any other suggestions?
Thanks, by the way, for your amazingly fast responses! |
|
|
|
| Tom |
| |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2008-07-24 11:13:28 |
| You will need to close the DB and MS Access to actually close the connection. |
|
|
|
|