<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: determine files open in LabVIEW</title>
    <link>https://ni.lithium.com/t5/LabVIEW/determine-files-open/m-p/184036#M106919</link>
    <description>Hi,&lt;BR /&gt;
&lt;BR /&gt;
The only way to do this is to make a custom "open file" that stores all references (in a buffer vi). The close vi can remove references that are closed. The buffer will have a list of and all unclosed file references, so a close all is easy to make.&lt;BR /&gt;
&lt;BR /&gt;
Regards,&lt;BR /&gt;
&lt;BR /&gt;
Wiebe.&lt;BR /&gt;
  "Castechvb" &amp;lt;x@no.email&amp;gt; wrote in message news:183705@exchange.ni.com...&lt;BR /&gt;
  Hi,&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;I had an issue with LabVIEW apparently not closing files correctly after writing to them. After some time spent checking and trying different things I found that it was actually the network server locking them and not labview!&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;My question is this though, is it possible to get a list of open files from labview OR is there a generic 'Close All' files facility? (Note: It is input or output files I want a list of not open VI's.). It would have been very useful to have been able to check.</description>
    <pubDate>Thu, 17 Feb 2005 08:10:40 GMT</pubDate>
    <dc:creator>Wiebe@CARYA</dc:creator>
    <dc:date>2005-02-17T08:10:40Z</dc:date>
    <item>
      <title>determine files open</title>
      <link>https://ni.lithium.com/t5/LabVIEW/determine-files-open/m-p/183705#M106748</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I had an issue with LabVIEW apparently not closing files correctly after writing to them. After some time spent checking and trying different things I found that it was actually the network server locking them and not labview!&lt;BR /&gt;&lt;BR /&gt;My question is this though, is it possible to get a list of open files from labview OR is there a generic 'Close All' files facility? (Note: It is input or output files I want a list of not open VI's.). It would have been very useful to have been able to check.</description>
      <pubDate>Wed, 16 Feb 2005 14:42:45 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/determine-files-open/m-p/183705#M106748</guid>
      <dc:creator>Castechvb</dc:creator>
      <dc:date>2005-02-16T14:42:45Z</dc:date>
    </item>
    <item>
      <title>Re: determine files open</title>
      <link>https://ni.lithium.com/t5/LabVIEW/determine-files-open/m-p/184036#M106919</link>
      <description>Hi,&lt;BR /&gt;
&lt;BR /&gt;
The only way to do this is to make a custom "open file" that stores all references (in a buffer vi). The close vi can remove references that are closed. The buffer will have a list of and all unclosed file references, so a close all is easy to make.&lt;BR /&gt;
&lt;BR /&gt;
Regards,&lt;BR /&gt;
&lt;BR /&gt;
Wiebe.&lt;BR /&gt;
  "Castechvb" &amp;lt;x@no.email&amp;gt; wrote in message news:183705@exchange.ni.com...&lt;BR /&gt;
  Hi,&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;I had an issue with LabVIEW apparently not closing files correctly after writing to them. After some time spent checking and trying different things I found that it was actually the network server locking them and not labview!&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;My question is this though, is it possible to get a list of open files from labview OR is there a generic 'Close All' files facility? (Note: It is input or output files I want a list of not open VI's.). It would have been very useful to have been able to check.</description>
      <pubDate>Thu, 17 Feb 2005 08:10:40 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/determine-files-open/m-p/184036#M106919</guid>
      <dc:creator>Wiebe@CARYA</dc:creator>
      <dc:date>2005-02-17T08:10:40Z</dc:date>
    </item>
  </channel>
</rss>

