02-08-2006 08:06 AM
02-09-2006 12:19 PM
The Only way to do this is to use a module of some sort. Even if you would have to call the System32.dll you would still have to use a module. Is there a specific reason why you NEED to do it directly from TestStand?
If you wanted to do it through ActiveX then Microsoft would have to provide some sort of API that would allow you to make system calls like that.
02-09-2006 12:28 PM
Ok, thanks. The reason why I wanted to have it done inside teststand is because I want to reduce the dependence of my custom step types on external code modules. Having it done through a LabVIEW VI is great and easy, but its one more file to maintain.
Anuj
02-13-2006 08:33 AM
I was able to do this, I am not sure if you had understood my question, but it turned out to be fairly simple. This is how it can be done:
1) Insert an ActiveX/COM action step.
2) Choose the automation server as Microsoft Scripting Runtime (Ver 1.0)
3) Choose the object class as FileSystemObject (IFileSystem3).
4) Call method CopyFile.
Anuj
02-28-2006 08:48 AM
02-28-2006 09:25 AM
Instead of using a reference of an already created object, I just created a new object for this. So when you choose the object class, right below that, check mark the option 'Create Object'. Thats all you need to do.
Let me know if it doesn't work.
Anuj
02-28-2006 10:39 AM