12-17-2007 09:19 PM
12-18-2007 02:38 PM
Hi Matt,
From my understanding of what you are trying to do here, I believe this can be done by carefully using the List Folder VI from the File I/O >> Adv File Functions palette. In using this VI you would need to include *.tdm as the pattern input, which would in turn populate an output array with all of the files in that directory with that extension. This array will have all of the TDM files listed as strings which you can then build a path for each file to parse through for your desired text. It should only look for that extension in the top directory, so if there are sub directories that also need to be searched, then you can get a list of these directories and perform this same search.
I hope this helps. Regards,
Jason W.
12-19-2007 11:16 AM - edited 12-19-2007 11:17 AM

12-20-2007 05:44 AM
All,
Unless I am missing something this doesn’t answer my question. I need to generate a list of files that that contain information about the equipment tested within the file and not in the file name. List file will filter the names of the file and not the data within the file. The reason I am not using DIAdem is that I have a very simple requirement to list the files and I don’t need to mine the data for information. Let me know if there is a way without having to open every file.
12-21-2007 09:58 AM
12-21-2007
10:36 AM
- last edited on
10-23-2026
04:22 PM
by
Content Cleaner
I would agree with Jason. While this may seem like a fairly basic operation to just "list the files containing the correct information" from the eyes of the programmer, it's actually pretty detailed. In order for LabVIEW to gain access to the metadata of the files you're trying to search, a few steps are going to be involved. As Jason suggested, if you'd like to achieve this In LabVIEW, you'd have to programmatically:
In a way, you're creating your own custom indexer to retrieve the desired information from your set of files.
The reason I suggested DIAdem for this application is that, as I previously stated, this is basic functionality within DIAdem - the work is all done for you behind the scenes (hence the "mining" of data that you describe) by the DataFinder that uses minimal system resources in the background to index your data That way, when you need to quickly search for certain criteria and list the files that apply to the situation, a programmatic routine like the one above isn't necessary; DIAdem simply references the information it has already collected in the course of its indexing. I think this is perhaps one of DIAdem's strongest points - ease of data management.
I hope this helps clarify the situation!