There are two options which you can try: + You can manually build the MenuItem collection of the Menu control based on the XML data. + You may try with the XmlDataSource[^] control.

Hi PogoWolf I don't know whether you have sufficient static HTML wrappers lying around, so you don't want to do it all by creating ASCX files instead. But if you want to load a Web User Control dynamically from another Web User Control (WUC hereafter), then you have to store information about what should be loaded somewhere that the WUC can get to it. For example Session, ViewState, QueryString, etc. In that case there is no problem with for example loading the following variables in Session: Session["mainControl"] = "usercontrols/Comments.ascx"; Session["subControl"] = "usercontrols/AddComment.ascx"; Then the ASPX Page could just look in Session["mainControl"] for what WUC to load, and the "Comments.ascx" WUC could look in Session["subControl"] for what WUC to load inside itself. Hope this helps, otherwise ask again. Kind regards - Jakob :cool: Three kinds of people in the world: - Those who can count.. - Those who can't!

o worked on paper airplane a long time ago. it was trying to imitate wiki Its in java but c# is basically the same. It should be open source if its still around 1 line of code equals many bugs. So don't write any!!

That's not what I've heard. http://www.devsource.com/article2/0,1895,1929552,00.asp[^] However, I should also state that VB6 is on its last leg and is not getting much support from Microsoft. It'll be in your best interest to migrate your VB6 code to .NET or whatever your language of choice is.

Thanks for the link Ista. and thanks again for the response. =) -== The PogoWolf ==- Like a funkey muckin' a bootfall. http://www.pogowolf.com GamersVue: ttp://GamersVue.blogger.com

Well lets look at it this way You have a multitude of classes to display a report. Each class represent a particular behavior. And each class may/may not contain addition class objects to represent additional custom behavior. That needs a composite design to supply additional behavior. Much like an assembly line with additional bays. Each bay has at least one conveyor belt for assembly. But each bay may contain additional bays also. Look at it that way. So based on a composite design pattern we can build the entire report. Create interfaceA that will have all actions needed like newObject, dataGrid, Parent. Not the exact methods and properties but you get the drift. Now that you have the report organized and resembling true functions and access is governed by an interface to allow for needed polymorhism to access additional composites. Now lets talk about access your report. You would want a factory to produce the report object. Take a look and say is there any access that might need thread safe actions? I suggest a abstract factory with a singleton pattern. The reason, and I could be wrong since I'm not there. But, this sounds like herogenous data source which means if 2 threads hit the data source at one time it would block the other from getting to the data. So decide do I need mutiple factories or just one. Also set the module property also depending if you can re-use. But if you have multiple factories make sure there will not be locking. So basically what it will do. Create a handler that will access propert types like .sqlx files. Create a handler class that will get your factory. Call GetReport passing the needed parameters. This factory will return the composite interface Then add this composite to your page. Then tell the page to call RenderControl on your object, thus building your page singleton basicall is this private static _object = null; public static singleton GetFactory { if _object == null _object = new singleton(); return _object } thats a simple singleton. As you can see we get a reference from calling a static property. The contructor needs to private. For a factory class it just needs one method public IComposite GetReport( ... parameters ... ) { create the composite needs } interface maybe defined as public interface IComposite { IComposite Control{get; set;} DataGrid DataGrid{get; set;} ... more ... } this way the functions are the same and they use polymorphism Now you don't have to do this but it wil