>>Then your point is a peripheral issue. He is being ragged upon because he claimed that macro substitution would work in one and not another. Everything else was just clarification.
>
>I might be missing something here, but I thought this was the original problem - that it did work in one but not the other. Andrew was just trying to put forward his idea of why that should be (backed up with a maybe).

But it does work as proven by the following code:

LOCAL cPath, oApp

cPath = SET('path')
CLEAR

? set('path')
oApp = CREATEOBJECT('TestClass')
? set('path')

SET PATH TO (cPath)
? set('path')

DEFINE CLASS TestClass AS CUSTOM
	PROCEDURE init
	LOCAL cPath
	cPath = "C:\"
	
	SET PATH TO &cPath
	RETURN
	ENDPROC
ENDDEFINE

Generates no errors. And LOOK there's a macros substitution in the code for the class. Will wonders never cease.

And there was nothing for Nancy to clarify, because I'll bet that she, like me, doesn't know why Lucien thinks it doesn't work, but what we do know is that what's his name was blowing smoke out his a**.

You want rude? I'll tell you what rude is - rude is that fact that everyone sits here defending some poor sot who loves to watch himself type while no one has helped Lucien. And one person after another wants to wag their finger in Nancy's face, while we ignore the real problem.

Get a life, get a grip, let's deal with the real problem.