Ok, I figured out my own answer. I ended up comparing my old DNN6 Code to the new DNN7 Code, and I had to also download the DNN 7.4.1 Platform Source and review to code in the framework, and finally got a solution.

For anyone else having this same problem, do the following:

1) First perform a recursive search within the DNNTextEditor control for another control of the type Telerik.Web.Ui.RadEditor
- In DNN6 this usually returns a control, in DNN7 in most cases it returns nothing
2) Next, If you still have no control from the above code, then do a recursive search for a control of type Telerik.Web.UI.RadDialogOpener
- This should ALWAYS return to you a control object
A) Now that you have a RadDialogOpener control, take it's parent and cast it to a Telerik.Web.UI.RadEditor contol
- Note: You might notice that the parent of the RadDialogOpener Control is of type DnnEditor, don't worry as DnnEditor inherits from RadEditor so the type cast will work.

Now you can access the RadEditor controls and features through intelli-sense off the RadEditor object.

If you need to "test" to see if you successfully retrieved the RadEditor control reference, for DNN7 you have to perform a duel test:
((objControl.GetType() IsNot GetType(Telerik.Web.UI.RadEditor)) And (objControl.GetType().ToString() <> "DotNetNuke.RadEditorProvider.Components.DnnEditor"))

If the above line is TRUE, then you need to perform the recursive search as explained above. If the above line returns FALSE, then you have a valid RadEditor control reference.

I created methods to do the above recursive searching to make things easier and modular so you may want to consider doing the same.

Have fun coding!

---

Ben Santiago, MCP Certified & A+ Certified
Programmer Analyst
(SQL, FoxPro, VB, VB.Net, Java, HTML, ASP, JSP, VBS, Cognos ReportNet)