@Ed, It's probably the compatibility option: " Use 4DVAR Comments instead of Brackets: This option sets the notation to use when inserting 4D expressions on static pages. When the option is checked (default value), the syntax you need to use is the standard HTML notation (<!--4DVAR MAVAR-->). " http://doc.4d.com/4Dv15/4D/15.4/Compatibility-page.300-3285389.en.html
@Ronald the Compatibility note you mentioned is in reference to the variable defined in the calling context. see the following examples: $tVar:="this is a local variable" // this is the calling context vtText:="<!--4Dvar $tVar-->" // this references the local variable $tVar from the calling context // when vtText is evaluated the local variable $tVar will be undefined because the execution context is different from the calling context vs tVar:="this is a process variable" // this is the calling context $vtText:="<!--4Dvar tVar-->" // this references the process variable tVar from the calling context // when $vtText is evaluated the process variable tVar will be defined because the execution context of PROCESS 4D TAGS is still in the same process as the calling context. -Tim PENNER ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
