If you are using a fex to launch your HTML page then you can use the "old" method of populating SELECTS.
In you fex include an extract -
FILEDEF CONSSELS DISK CONSSELS.FTM
-RUN
-WRITE CONSSELS <OPTION VALUE=FOC_NONE SELECTED>ALL</OPTION>
-RUN
FILEDEF CONSSELS DISK CONSSELS.FTM (APPEND
-RUN
DEFINE FILE CONSTRUCTION_PLANS
OPTION/A95 = '<OPTION VALUE=' || SCHEDULE_ID || '>' || SCHEDULE_ID || '</OPTION>' ;
END
TABLE FILE CONSTRUCTION_PLANS
PRINT OPTION
WHERE ( SCHEDULE_ID EQ &schedule.(FIND PLANS.SCHEDULE_ID IN PLANS.schedule. )
ON TABLE SAVE AS CONSSELS FORMAT ALPHA
END
-RUN
-HTMLFORM what_ever_your_HTML_is_called
and then in your HTML you would change your SELECT to something like -
<SELECT style="Z-INDEX: 5; LEFT: 420px; WIDTH: 150px; POSITION: absolute; TOP: 200px; HEIGHT: 22px">
!IBI.FIL.CONSSELS;
</SELECT>
The downside to this is that it is no longer controlled by the DHTML methods employed via the ibirls.js javascript module and hence the ability to chain it into relationship with other SELECTS.
The DHTML methods actually use ActiveX to interpret an XML file created using an adhoc fex on the fly (created and executed in the JS) which is why the dynamic chaining works.
To retain the dynamic chaining you could reproduce the IB javascript to build your own XML file on the fly (I have done it but it doesn't make for reuseable code
).
Have fun establishing your solution and please let us know what you decide upon.
T