I agree that the cookie header manipulation is cumbersome.

What I have done in these instances is to use STRTRAN to write the HTML cookie code into the template. You could use:

 lcWholeShebang=o.ExpandTemplate(lcPageName, lcContentType, llTemplateString, .T.)
lcWholeShebang=STRTRAN(lcWholeShebang,PlaceHolder,lcCookieString)
Response.Write(lcWholeShebang)

In fact, I use this technique for everything ExpandTemplate does.

HTH

>>You can create a separate header object, then pass that in to ExpandTemplate as a parameter (see lvContentType below, from the docs for ExpandTemplate):
>>

>>o.ExpandTemplate(lcPageName, lcContentType, llTemplateString, llNoOutput)
>>
>>lvContentType
>>Optional - Either an wwHTTPHeader object or content type string. See wwHTTPHeader class for info.
>>

>
>Yes, I know. This doesn't help. As a header is still created. On the second call to ExpandTemplate(), another header will be created. Or, even if I call it only once, what if I have to add a cookie after I did the call. I'll face the same situation.