Problem with database connectivity toolkit

[ManiAm]

I have problem with Labview database connectivity toolkit. I build and deploy the real_web.vi (attached to the post) to the web server. It seems that the DB Tools Open Connect can not connect to the data base, and it issues the following error:

NI_Database_API.lvlib:DB Tools Open Connec (String).vi->real_web.vi->real_web.vi.ProxyCallerADO Error: 0x80004005 Exception occured in Microsoft OLE DB Provider for ODBC Drivers: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified in NI_Database_API.lvlib:DB Tools Open Connec (String).vi->real_web.vi->real_web.vi.ProxyCaller

But in highlight execution, I do not get this error! My program connects to the database and read the data. What is wrong ?

Moreover, when I connect to the vi using the web-browser, the cpu usage of ApplicationWebServer process goes up to 100% (The same problem as stated in this post). 

[mikeporter]

Say what you will about the problems that the DCT can cause (and goodness knows I have) my suspicion is that this is not a toolkit ptoblem. When ever something only works with execution highlighting on, two words should immediately jump to mind: "race" "condition".

Execution highlighting will muck aound with the order in which things get done in your code. Can you post what your code looks like?

Mike...

[ManiAm]

Thank you mikeporter for the reply. I have already attached the code to the first post.

But, I found the problem yesterday. The problem was (as labview complained) about the ODBC. Previously I defined my database DSN under User DSN, but now I moved it to System DSN. As a result, everything is working smoothly! (although it seems a little bit odd).

[mikeporter]

This is more than a bit odd. The code should work the same regardless of whether or not execution highlighting is on. I would still want to know why the error went away with highlighting on.
Mike...