Comments on: Cleaning Pasted Code

By: Mister Ians Weblog from Kuwait » Daily Dose of Excel » Blog Archive » Cleaning Pasted Code

Tue, 24 Oct 2006 20:29:00 +0000

[...] Daily Dose of Excel » Blog Archive » Cleaning Pasted Code [...]

By: Dick Kusleika

Dick Kusleika — Wed, 18 Oct 2006 18:11:00 +0000

Good guess Alderaic. I don’t know how the code gets into Word. Not all of the code has screwed up qutoes, but it’s pretty easy to tell which does and which doesn’t. I assumed it was a curly quote autocorrect thing, but John’s experiments seem to dispell that theory.

By: Alderaic

Alderaic — Wed, 18 Oct 2006 17:31:00 +0000

I assume all that is related to writing books

my personnal way to store procedures etc.. is to use scite, it works just fine and doesnt add any fancy things (but still recognize syntax etc…), and save as txt file

(I say that because I assume that your code is coming from a vb editor first then goes into word and back into a vb editor, I would not imagine writing code straight into word)

By: Juan Pablo Gonzalez

Juan Pablo Gonzalez — Wed, 18 Oct 2006 15:58:00 +0000

I would include Chr(160) as well ? (replace it with Chr(32)

By: John Walkenbach

John Walkenbach — Wed, 18 Oct 2006 14:14:00 +0000

That’s strange, I don’t have a problem with pasting from Word. Even if I turn on the smart quotes option in Word, (using Tools – AutoCorrect – AutoFormat As You Type), those funky quotes are converted to normal quotes when I paste into a VBA module.

I wonder what causes the difference?

By: Jon Peltier

Jon Peltier — Wed, 18 Oct 2006 04:44:00 +0000

Don't forget 145:

sCode = Replace$(sCode, Chr$(145), Chr$(39))

145 and 146 are the curly open and close single quotes. 147 and 148 are the corresponding double quotes.