Copying/Pasting in more than one Excel file from TestStand

[parkerfly]

We are using TestStand 3.5 and LabVIEW 8.0 with the Microsoft Office Toolkit.  I'm trying to find a way to copy a range of cells from one file to another file using TestStand.  My test would have both files open, but I'm not sure how to copy cells from one file to another one.  I found several posts, but none seem to show me what I'm looking for - there were a couple that do copy/pasting, but they use a different way to reference the Excel file.  The toolkit generates a number to use as a reference to a file that is opened/created, but all the examples I've found on the forum use a different type of reference to indicate a file and I've not been able to figure out how to translate from one format to the other.

Ideally this would all be done by calling vi's directly from TestStand that already exist, although we can create new vi's if needed.

Anyone have any idea how I can do this?

[RayFarmer]

Hi,

I haven't got this Toolkit available to me, but I would have thought that you would have to perform two opened/created calls, one for each file. I wouldn't have thought you would what to return that data back into TestStand, then to pass it back to another VI to do the pasting but maybe leave it in LabVIEW in maybe a global, if you wanted to pop back to TestStand.

It would probably be easier to have one VI, that took the two file references, (maybe the sheet reference) and the cell ranges then perfrom the task then return back to TestStand.

Regards

Ray Farmer

[parkerfly]

Actually, if there was some way to copy to the clipboard from file 1, then paste from the clipboard into file 2, that would work as well.  I'm thinking that might be the easiest way to do it, but I've not been able to figure that out yet....

[Josh_W]

Parkerfly,

Since the bulk of the work is being done by LabVIEW and the Office Tookit, you might have better luck if you post your question to the LabVIEW forum.  Once you have a VI that does the operations you are looking for, it should be simple to call from a TestStand sequence.