Problem with DB Toolkit in a built application

[John_Howard]

I think this is a bug, but my brain is so fried from the last 10 hours of troubleshooting, perhaps I am missing something.

When I build an application in LV 8.2 using the Database connectivity toolkit (version 1.0.132), it builds fine, but when I try to run the .exe, I get a message just saying that the program is not executable, and I need to run in the development environment to troubleshoot (it runs fine in the development environment).  If I build the application with debugging enabled, it runs fine, so I can't troubleshoot that way either.

I finally discovered that if I put all the DB toolkit vi's into sub-vi's (don't call them directly from the top-level vi), then everything works great again!  (There may be more to it than this - I actually hid the DB toolkit vi's in a LVOOP class to get the .exe running again.)

Anyway - has anyone else observed this or similar behaviour?  Should I report this as a bug?

Thanks!

John

[tbd]

Hi John,

      When the .exe is launched, does it immediately display a broken-arrow, or does it run and pop-up an error dialog?  Is it possible this error happens at a "dynamic" call?

Cheers!

[John_Howard]

When the .exe tries to run I get an instant broken arrow - it appears that it is not even trying to run.

Does this mean it could be a dynamic call?

[John_Howard]

Just one more piece of additional information.

I've attempted to make a small example VI to reproduce this behaviour, and so far I can't.  Everything works just fine in the smaller app.

If I manage to narrow down the interation that is causing this I'll post further information.  However, since my application is working now, I can't afford to spend too much time investigating this.

Thanks to all for a great forum!

John