Since the upgrade to QuickBooks 2008 and QODBC for QuickBooks Version 8, the daily job that transfers data from Alpha to QuickBooks completes the data transfer successfully but then remains logged into QuickBooks until the job is manually terminated. QODBC is tying up our third user licence on QuickBooks and the nightly backup job is skipping the QuickBooks data files as they are "opened by another process." 

Termination problem persists:

On 11/12/2005 we joined our business software (Alpha5V7) with our accounting software QuickBooks 2005 using Flexquartes QODBC and for over two years have had a marriage made in heaven. 

Along comes QuickBooks 2008 which now requires a QODBC version 8 Driver.  Using the same Alpha script (xbasic) we now experience a problem in that QODBC at the conclusion of the transfer fails to terminate.  Nightly I manually terminate the batch job which then closes the QB files.

We read that an “EndSession” command is recommended but this command is not supported by xbasic.  We have lengthened the closing time to 600 seconds and still have the problem.  Last evening at 10:00 PM (Sunday) I opened the Task manager and noted that just two Applications were running, neither being Alpha5 or QuickBooks yet Alpha was logged into QB and only when I “terminated” the batch job using the Task Manager (Processes tab) were the ties to QB severed.

As you can tell by the written words above, I am the end user, not a programmer. My goal is to return to running our business so any suggestions are greatly appreciated.

There are no messages in the QODBC log.  Any other suggestions?

When the Alpha script (xbasic) is run standalone we may or may not experience the same problem as we do when we run the nightly batch job, This morning at 6:00 AM with no one on the system we were able to run the script and move data to QB successfully twice and the job did not hang up.  Manual runs have very little data and take only 10 to 15 seconds. But this is not always true, some days we are not able to run the script without the job hanging up each and every time.  If the standalone job does hang up, we cannot run the script again until we manually terminate the previous job as we get the message “Not able to connect to QB.”  However, we can run the batch job over and over again even with Alpha5 logged on from a previous job.

Our code to QB is pretty tight and all the updates are occurring OK.  We are not getting any error messages, there are no QODBC error messages, and the last time we checked the QB log, there were no messages. If it is QuickBooks that is not allowing the file to be closed, this would not be due to contention with other users, because no one is logged on. We do not believe that we have a bad SQL command or update that causes things to hang as the updates are working fine.

We tried running the BATCH JOB piece by piece and it hung up each and every time. Yesterday, we successfully ran the QODBC update job “STANDALONE” 4 times with Alpha5 logging off QuickBooks and the job terminating without manual assistance all four times.  We started with only updating the data on one customer and worked up to doing 4 updates in one run.  However, on the fifth try, updating only 3 of the same customers, Alpha5 failed to log-off QuickBooks and we had to manually terminate the process using the task manager. 

 At this point, we WELCOME any suggestions on how we should proceed in determining what is causing the hang-up?