01-29-2009 06:45 PM
I'm trying to update this thread with what I have found.
2 computers with this problem is running on Windows2000. The other computer seems to be O.K. is on XP.
Cheers.
Steve
02-02-2009 09:44 AM
Hello Steve,
I noticed you are using some VIs that are no longer supported/suggested. For example, the help for both the File Dialog and Open_Create_Replace File VIs suggest that you use different VIs instead. I would suggest replacing these VIs with the new supported versions. Also, if this does not solve the issue, try to narrow the code down to the exact VI that causes the hang.
02-02-2009 07:16 PM
Hi Burt,
How can I get newer VIs? Does it involve upgrading LabView?
Is there any other way to use the newest VIs in LabView 7.1 ?
Thank you in advance.
Steve
02-03-2009 10:03 AM
02-03-2009 11:38 PM
Hi, Burt
I was able to narrow down a little bit more today. It happens only when application file is located in remote (server) computer. If I run it from local C drive, it is alright. I really prefer to deploy application in server rather than each computer because it is simply make things easier as you can expect. A simple application built based on a "file dialog" shows exactly same problem. I'd like to summary the situation here.
1. Application builit on LavView 7.1 hangs.
2. File dialog.vi seems to be the smoking gun. (don't forget it's version 7.1)
3. Application in server is hangs. application in local drive seems to be O.K.
4. Two P.C. that hang is run on Windows2K. what else...hmm.. that's all for now. ah!
5. It was O.K before IT guy changed the log in and password of each computer.
Thank you.
Steve
02-04-2009 09:00 AM
Hello Steve,
Unfortunately your set-up would take me a while to reproduce. However, if the File Dialog.vi is causing the problem, couldn't you just use the Open/Create/Replace File.vi with an unwired path input so that it pops up a file dialog? You could even wire your constant path into the Open/Create/Replace File.vi's 'start path' input and should have the same functionality you had before but hopefully without any hangs. Also don't forget to put the original Open/Create/Replace File.vi into the no error case so that the output of the case structure is a file reference instead of a file path. Let me know if this helps or if I am missing something again.
02-05-2009 04:36 PM
Hi Burt,
Open/Creat/Replace File.vi still has same problem. Not surprising because it contains "File dialog" function (I realize it is not vi) in it.
I already tried hardwiring file path to known directory without any good results. By the way could you explain the last bit you suggested about case structure and refnums? I couldn't get it.
Thank you again.
Steve
02-06-2009 12:02 PM
Hello Steve,
Unfortunately I am running out of ideas. I don't know what else to try other than to look for a workaround. You mentioned before that wiring a constant path did not work. What would happen? It looks like your best option would be to try and avoid using this VI anywhere in your application. Let me know what happens with the File Path constant.