Azazel Posted November 16, 2004 Report Posted November 16, 2004 Hello all, I recently upgraded from labview 7.0 to 7.1. Before the upgrade my vi's worked fine. After the upgrade my programs keep crapping out at a section in my code where I create a new folder dependant on user information. Has any one experienced this problem before? I think it is frikin weird and I can't figure out why this is occuring. Any thoughts? Quote
Jim Kring Posted November 16, 2004 Report Posted November 16, 2004 Hello all,I recently upgraded from labview 7.0 to 7.1. Before the upgrade my vi's worked fine. After the upgrade my programs keep crapping out at a section in my code where I create a new folder dependant on user information. Has any one experienced this problem before? I think it is frikin weird and I can't figure out why this is occuring. Any thoughts? 2668[/snapback] I've noticed some File I/O problems when trying to delete files. It seems as if it is a permissions problem. Perhaps LabVIEW is locking the file and not releasing it, causing subsequent operations to fail. What does your code do, specifically? Can you post an example? -Jim Quote
Azazel Posted November 17, 2004 Author Report Posted November 17, 2004 I've noticed some File I/O problems when trying to delete files. It seems as if it is a permissions problem. Perhaps LabVIEW is locking the file and not releasing it, causing subsequent operations to fail.What does your code do, specifically? Can you post an example? -Jim 2669[/snapback] It seems there are some new error handling capabilities in 7.1. In my old code when I was creating a path, but with nothing in the control string, it would sipple state <not a path> and continue on its merry way. In 7.1, a error window pops up with the same <not a path> stopping my code. I went to the options menu and turned off error handling dialoge box and the code works again. I guess this option would be good for some codes but not mine. Azazel Quote
didierj Posted November 18, 2004 Report Posted November 18, 2004 I guess this option would be good for some codes but not mine. 2678[/snapback] It is usable (in some ways), when you're debugging and don't want to step through your whole code. So you get an idea where and when your error occurs. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.