Thank you ahead of time for the help.
I have some vba code that has been working flawlessley on my machine. Essentially, I use vba to create an email and attach a personal signature from outlook. The part of my code that has worked and is now in question is this:
This finds the file fine on my machine and the email is created nicely. When I go to the folder and select the file, the path is this:
file:///C:/Users/whitekv/AppData/Roaming/Microsoft/Signatures/Standard.htm
I am trying to run the code on a co-workers machine and not getting the signature to attach to the email because when we click on the signature file, the path is this:
file:///C:/Users/Nayran/AppData/Roaming/Microsoft/Signatures/Standard%20.htm
You can see that he has the extra %20 on the end of his filename. How so I remove this or what is the most effective way to make his machine interpret the filepath like mine does? The code does not locate the file because of the %20 added to the end.
Thank you!
I have some vba code that has been working flawlessley on my machine. Essentially, I use vba to create an email and attach a personal signature from outlook. The part of my code that has worked and is now in question is this:
Code:
SigString = Environ("appdata") & "\Microsoft\Signatures\Standard.htm"
If Dir(SigString, vbNormal) <> "" Then
Signature = GetBoiler(SigString)
Else
Signature = ""
End If
This finds the file fine on my machine and the email is created nicely. When I go to the folder and select the file, the path is this:
file:///C:/Users/whitekv/AppData/Roaming/Microsoft/Signatures/Standard.htm
I am trying to run the code on a co-workers machine and not getting the signature to attach to the email because when we click on the signature file, the path is this:
file:///C:/Users/Nayran/AppData/Roaming/Microsoft/Signatures/Standard%20.htm
You can see that he has the extra %20 on the end of his filename. How so I remove this or what is the most effective way to make his machine interpret the filepath like mine does? The code does not locate the file because of the %20 added to the end.
Thank you!