Paul,
Thanks again for your reply. I have tried referring to the .dll while it was located in the same file as the script.
This is still to no avail.
I read that the same error 126 can be caused by either referencing your library file location incorrectly, OR by not having installed any windows libraries that the target might be dependent on.
So are there any mission critical dependencies that I could be missing to load ssc32.dll properly.
I'm go to try this out on another machine in the meantime...
Cheers!
