@lysko wrote:
about the 1st question - Did the function open file work this way in the previous versions of LabVIEW? To the engineers from NI - what is the logic behind disallowing relative path specification for "open file"???
Thank you.
The concept of allowing relative path names to file functions is not a very clean one. It is based on the assumption that there is some hidden global variable specifying the "current directory". While Windows does do that (which IMO is a historical ballast from DOS days) it is not a concept easily translated to other operating systems.
Command shells have such a concept but programming APIs often not. Just consider the implications for an OS of maintaining current directories on a per process basis, which Windows does bother to do, but no other OS as far as I'm aware. LabVIEW as multiplattform environment has to make sometimes some decisions as to what not to support, because it can't be easily emulated on other platforms.
For me the concept of relative paths for file functions is confusing at least. Depending on other operations you may have done (opening the file selection dialog for instance chances the the current path for that process on Windows) the file may suddenly be accessed in a differnt location than before.
Rolf Kalbermatter
Rolf Kalbermatter
My Blog 
DEMO, Electronic and Mechanical Support department, room 36.LB00.390