11-16-2005 06:04 PM
11-16-2005 11:49 PM
Hi Manny,
Proper file handling and, especially array (memory) allocation can make a huge difference. But the diagram differences may be subtle.
Mind sharing the "slow" code? Maybe you're missing a shortcut (or two). ![]()
11-17-2005 04:09 AM
hi there
you could use the windows command "find" with the system exec vi. type "find /?" on a command shell or see the windows online documentation. another solution would be to get a windows - version of "Grep". this is similar to "Find" but much more powerful (search of trees, regular expressions etc.)
11-17-2005 10:32 AM
11-17-2005 01:34 PM
Find String (grep) Utility has encountered a problem and needs to close. We are sorry for the inconvenience
11-19-2005 07:57 AM
11-21-2005 08:19 AM
Hi JLS,
Even a simple systemexec with a string such as find /i "56743" \\DataServer\ExcelFiles alone on vi produces this error. In fact, even an erroneous use of the find(grep) command such as wiring only the find string to the systemexec command line generates the error. I've tried putting the command in the batch file and tried it on several pc's. It's doing the same thing so I am guessing that it might actually be a LabView bug. I am using LabView 7.1 on a Windows XP computer. The command works fine in a simple command line (not using LabView). It also works by executing a batch file on Windows containing the command. Use it in system exec, however, and it produces the error.
Attached are some screenshots of both the very simple block diagram and the error that gets generated.
11-21-2005 08:39 AM
hi there
i can reproduce the error you described. when connection the "standard input" - control the system exec - call works fine (probably the find.exe reads stdin()). see attachment...
btw.: i've seen a function findstr.exe. this supports regular expressions. see windows online help for more.
11-21-2005 09:03 AM