Pjotr

That's right indeed: The DB Tools Insert Data.vi and DB Tools Select Data.vi (LabVIEW 8.5 + database toolkit) work absolutely fine if you use the 'Oracle Provider for OLE DB', but not with the 'Microsoft OLE DB Provider for ODBC Drivers', which not goes beyond a rediculous 1000 bytes or so. Oracle database entry of files and images from LabVIEW made very easy!

I would like your opinions on the following: :gathering: From 8.20 (or probably 8.00 which I have not used) admin rights are required to install LabVIEW based executables, the LabVIEW run time engine and e.g. serial support through VISA. In my company end-users do not have these rights, therefore I would be forced to go through our IT departments to get the applications scripted and distributed, a process that takes minimally 2 weeks/iteration, reason to stick to LabVIEW 7.1 for the moment. Since my previous entry on this topic in this forum, NI in the Netherlands have now contacted NI-hq and without further explanation have mailed back to me that there is nothing they can do for me. I feel that one of LabVIEW's strengths has always been that professional end-user applications can be delivered by laboratory-automation-experts (as contrary to IT experts) in an efficient, powerful and flexible way. The admin privilige that has now become a requirement certainly impacts on this negatively. In the meantime I have found out (thanks Ulrich&Arnoud!) that there is a workaround, being a copy of selected runtime files to the executable directory. This is surprising, because it shows that the funcamental mechanism for application distribution, LV's runtime library approach, is not necessary in the first place and I feel that NI should have supported this option in the application builder (one big executable) or make it more explicit in their documentation. Clarification from NI on this would be much appreciated. Vista will add more complexity to this. I am not sure at the moment if this will worsen or better the situation, but am afraid that it will be the first.

I can't see a way to programmatically size a string indicator and/or the window size to match its contents, such that it mimics the behaviour of the 'message' indicator of the One Button Dialog box. Anybody out there to help or to hint?

Thanks Ulrich, Interesting approach, but I think that NI really needs to solve this proper. LabVIEW has always been associated with fast coding of complex tasks in short iterations. An end-user distribution of stand alone applications is one of the primary requirements for this. Pjotr

After a smooth migration from LabVIEW 7.0 to 8.2 I found out that 8.2's run time engine needs (local) admin rights to install, in contrast with 7.0rte. In my company, with 100+ users of ready-built LV applications this means a huge overhead to deploy. I was forced to return and stick to LV 7.0 until this problem is solved by NI or otherwise. Please advice.

Yep, I got this same bug after a brand new LabVIEW 8.2 developers suite installation. It is definitely not a maybe-bug! I will report to NI today.