Since we need to explicitly allow excel to use ms scripting runtime dll before we can use FSO, does this mean the code cannot be used by anyone else?
thanks
Since we need to explicitly allow excel to use ms scripting runtime dll before we can use FSO, does this mean the code cannot be used by anyone else?
thanks
.
Not quite certain what your mean in your question. Let me say two things :
Excel is not very secure. By design it is almost impossible to protect VBA code from being accessed / used by others.
Because of the lack of security, anyone can access your code and do anything with it.
Do these comments answer your question ?
If you use late binding to the Scripting.FileSystemObject e.g.
the code can be used by anyone using Excel in Windows without specifically setting a reference to it as the appropriate DLL will be almost certainly be available.Dim FSO As Object Set FSO = CreateObject("Scripting.FileSystemObject")
Graham Mayor - MS MVP (Word) 2002-2019
Visit my web site for more programming tips and ready made processes
http://www.gmayor.com
Thank you for your response, I was curious because it would not run (gave error) if I did not set the reference. I will try on other machines and see now.
Regards