Michel,

>My codes seem not to be a problem when it's running but when I need a dynamic combobox (I generate the combobox with a SCAN and a cursor) in my web page, I have to put response.write command for all DHTML code lines to retreive Option value marker under the Select marker relative of the combobox. Otherwise the Option value markers appears on the top of the DHTML code (before de HEAD marker).

If this is in a template expansion, you don't need Response.Write in the template. You could put the combobox generation code into a separate procedure and call it with one line in the template, like this (spaces added so code will show):

< % = mycombocode() % >

You would place that line at the point in the page where the < SELECT > code belongs.

In PROCEDURE mycombocode (or mycombocode.prg) you would construct that portion of the HTML for the SELECT and multiple OPTIONS and return that as a character string from the procedure. That block of HTML would then be inserted into your page as the template is expanded.

Or, you can look at ExpandScript which would allow you to embed a multiline block of code into the template, where you could scan the table and build the multiple options.

In either case, WC evaluates all of those expressions where they are placed in the template, before sending the entire page into the response stream.