Thanks for the response. The behavior of SETENV can be changed during manual entry by surrounding the string in quotes. Is there no way to emulate this in DIESEL? Below is the full code:
^C^C_ID;
\-INSERT;
"Z:/DEPARTMENTS/Engineering/Master Block Library/Functional/Tags/TAG-OUT.dwg";
$M=$(GETVAR,LASTPOINT);;;;
L1-$(GETVAR,USERI1); <--inputs the first block attribute
$(GETENV,DEVNUM); <--inputs the second block attribute
$(GETENV,DESC); <--inputs the third block attribute
SETVAR;
USERI1;
$(+,1,$(GETVAR,USERI1)); <--increments the variable for the first block attribute (for next time this macro is called)
SETENV;
DESC;
$(SUBSTR,$(GETENV,DESC),1,$(-,$(STRLEN,$(GETENV,DESC)),1))$(+,1,$(SUBSTR,$(GETENV,DESC),$(STRLEN,$(GETENV,DESC)))) <--increments the last character of the variable for the third block attribute (for next time this macro is called)
The problem is with the variable which stores the third block attribute. It's default initial value would be something like "INPUT 2", and the space in the string is prematurely terminating the SETENV command. I can cut and paste the same line of code into MODEMACRO, and I get the results I want, so the code is correct. I just need a way to get the same string into SETENV (possibly by somehow enclosing it in quotes).
Thanks