mike5 Posted July 7, 2011 Report Posted July 7, 2011 Hi all. I know it's not strictly scripting related, but yesterday I was working with a script which tried to create a Control VI from a template. The script worked well in my development project, but as soon as I copied that script to appropriate location for the "right click menu", I started getting "file not found". The template file was next to my "script" VI. Does anyone have any ideas? Thank you and best regards, Mike Quote
Yair Posted July 7, 2011 Report Posted July 7, 2011 If you're getting a file not found errors, it's usually because of the way relative paths are built. The easiest thing to do is to display that path where LV expects to find the file. This should help in determining why it's pointing at a location other than where the file is. Quote
mike5 Posted July 7, 2011 Author Report Posted July 7, 2011 If you're getting a file not found errors, it's usually because of the way relative paths are built. The easiest thing to do is to display that path where LV expects to find the file. This should help in determining why it's pointing at a location other than where the file is. Actually in the error I get the absolute path, and it's pointing exactly at the file I'm interested in. Br, Mike Quote
crelf Posted July 7, 2011 Report Posted July 7, 2011 Does anyone have any ideas? Yeah - show us the code! Honestly, it could be a bunch of things, but without seeing the code, we're shooting in the dark. Quote
mike5 Posted July 8, 2011 Author Report Posted July 8, 2011 (edited) Damn. Now that I'm trying it again it works... They must be putting something in the water here. Thanks, Mike Edited July 8, 2011 by mike5 Quote
mike5 Posted July 11, 2011 Author Report Posted July 11, 2011 Damn you LabVIEW!!!! It's doing it again! I can see it. "DIR" can see, only labview can't see it! What's going on? Quote
mike5 Posted July 11, 2011 Author Report Posted July 11, 2011 (edited) This is what I'm talking about. Can anybody spot an error, because I sure cant. Thanks in advance, Mike Edited July 11, 2011 by mike5 Quote
crelf Posted July 14, 2011 Report Posted July 14, 2011 I just ran a few tests - I can't see what the problem is Quote
silmaril Posted July 14, 2011 Report Posted July 14, 2011 Does this only happen in the "Program Files (x86)" directory? Was this file created newly? This is a long shot, but maybe it has something to do with access privileges and the way Windows virtualizes writes to directories that you should not write to? Maybe for some reason, DIR shows the virtual directory content, but LV sees what's really there, because it used the wrong file API functions? Can you see this file in Windows Explorer? Can you see it when you log in as another user? 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.