Property Loader folder

[jtdavies]

I'm a new employee maintaining an existing TestStand application.

This application uses the Property Loader to get configuration data from an Excel file. It is working and used on the production line.

I'm tasked with making a new version for a different (but related) product line. Mostly I think I'm going to be modifying the Excel data.

My problem is that I can't find the Excel files. They are being opened and used so they exist somewhere on the production machine or on the network.

The TS code creates the filename without a path. I've looked in the folder where the sequence file is stored no Excel files.

I've searched the entire C drive and the only files that look right are old files from 2004 that are stored in a zip file. I think these files are just old backups.

So how can I find the Excel files?

Thank you for any suggestions.

[RayFarmer]

Hi,

Have a look at the actual sequence file and the properties of the PropertyLoader step(s).

Is it an execl file or is it a csv file.

Check the path, is this relative or absolute or is it obtain from a TestStand variable.

If its a variable, is it a constant or is it programmable generated.

Finally, are you sure the PropertyLoader step is being executed. (eg its not set to Skip) and therefore its actaully using the limits in the steps.

happy hunting

Regards

Ray Farmer

[jtdavies]

It's an xls file.

Here is the expression form the previous step which asks for the UUT.

Locals.PowerSupplyModel = Step.Result.Response + Str(".xls")

The source tab of the Property Loader has:

Locals.PowerSupplyModel

In a Windows program, if a file to be opened doesn't have a path in the file name it is assumed to be located in the same folder as the executable. If it is a dll, the system path is searched.

But I don't know how it works in LabView world. There has to be a path stored somewhere where I can't find it.

[jtdavies]

I'm a little further along. There is a folder on our server that contains all company documents. The Property Loader iterates through that folder and all subfolders until it finds the Excel file.

So the document folder namd has to be stored somewhere as a root. I just don't know where.

Yet.

[J_Stape]

Hi jtdavies,

Do you know the name of the excel file that is stored in the variable Locals.PowerSupplyModel?  If you do not, you can put a break statement on the Property Loader step so that you can see the value of Locals.PowerSupplyModel that is being passed to it.  You can view the current value of Locals.PowerSupplyModel by switching to the Variable tab (located at the bottom of the screen) and looking in the Locals section.

[RayFarmer]

Hi,

In this case it would be the same location as the sequencefiles.

Also assuming what you type in produces a valid filename!

Regards

Ray Farmer

Message Edited by Ray Farmer on 03-06-2008 06:41 AM

[jtdavies]

Jessica-

Locals.PowerSupplyModel is equal to 040-20000-00.xls (or 040-20000-01.xls, etc based on what is scanned in).

There is no path - just the file name.

That's what is confusing me, it knows the root path and knows to iterate through all subfolders until it finds a file by that name.

[jtdavies]

Found it!

Property Loader searches all the folders in Configure - Search Directories