INFO: Issues Regarding Converting DTCs to Run-Time Text

MORE INFORMATION

• By converting a DTC to text, the Design-Time Control itself is removed from the Web page, you will no longer be able to use the control itself or its Properties dialog box at design time.
• You can no longer use the Script Outline window to reference the script object or its events. The script object will not be present under node " "Client Objects & Events" or "Server Objects & Events" depending on the scripting platform selected.
• After converting a DTC to text, if you drag and drop an identical DTC to the Web page, it's possible to have a name conflict if one of the DTCs is not renamed. This can cause unexpected results if ignored.
  
  For example, if you convert a Textbox DTC(Textbox1) to text, and then drag and drop another Textbox DTC to the Web page, Visual InterDev will default its name to "Textbox1." If the first DTC already has a "Textbox1_onchange" event handler, clicking the "onchange" event in the Script Outline Window for object "Textbox1" will not create a separate event handler for the second DTC. It will simply move the cursor to the existing "Textbox1_onchange" event handler. If the first DTC does not already have a "Textbox1_onchange" event handler, Visual InterDev will create a "Textbox1_onchange" event handler, which becomes the event handler for both DTCs.
• If you have a DTC referenced by other DTCs, converting the DTC to text will cause functionality loss of DTCs that reference the DTC.
  
  For example, if you convert a Recordset DTC(Recordset1) to text and there is a Grid(Grid1) bounded to Recordset1, when you open your property Dialog Box of Grid1, "Recordset1" is marked in red, and there is no field available for selection. If you drag-drop another Grid (Grid2) to the Web page, it can no longer reference "recordset1" (both the recordset field and the available field are empty).