ODBC driver registration window

Question

We are using the ODBC driver for some read-only data access on a Windows 7 workstation with a Sage 100 ERP 2013 Advanced client installation also on the machine. For some reason, the very first ODBC connection that my application attempts causes the registration window to popup, which blocks the process until it is closed. This does not happen on my development machine, but, as far as I can tell, the client installations are the same. Any idea as to what might be the cause?

vbnet3d · Accepted Answer

Thank you for all your help - it should be helpful for anyone seeing this in the future in general. In our case, I tried everything you suggested, and had no luck. Everything matched what I should have been seeing. It turns out that this issue was actually a lot deeper. 
 
First off, the window was actually caused to be shown because the ODBC driver was being invoked with concurrent requests on the same user. My application is heavily multi-threaded, but I put in a number of safety checks to prevent concurrent requests of this nature. However, as I dug deeper into the problem, I discovered that the OS had somehow orphaned one of the child threads of my application, and kept it running long after the main process had ended. This orphaned thread did not show in Windows task manager or any other process monitor. I only discovered it through my own custom tools that were monitoring the application. The orphaned thread continued running, and this resulted in the collision when the complete application ran. 
 
So, note for future reference for developers: A registration window popup on ODBC calls may be caused by concurrent requests with the same user from multiple threads.

Sage 100

ODBC driver registration window

COMMUNITY

COMPANY

PARTNERS

SUPPORT & TRAINING