Hi akkram i think u can't directlly. but you can create custom datagrid view from the base gridw view. if you want to get sample source code from the Apress.com thanks Cheers,Earn and Enjoy RRave MCTS,MCPD http://ravesoft.blogspot.com

To use your UserControl within the VS Designer it has to have a default constructor. I see two solutions to your problem: 1) let everything the way it is now and add a property set what you have to set. 2) Add your UserControl dynamically (with the constructor with your parameters) in the Load event of your Form. If you want designer support then I'd suggest you use solution 1. The property value can be set either in the designer (if it is a constant value) or somewhere in the code. Happy coding -^-^-^-^-^-^-^-^-^-^-^- no code is free of bugs

When U Add A DataGridViewColumn See That The Enable Edting Property is Set To True Then To Add Rows Do THis : value toCol1Row1 = .... value toCol2Row1 = .... value toCol3Row1 = .... Where value ( int, string...) Gather all of the Variables to an Object array Object [] Row1 = {toCol1Row1 ,toCol2Row1 ,toCol3Row1 }; Add it to the DataGrdiView DataGrdiView.Rows.Add(Row1); While in your App u need to set the value of the CheckBox Column to either true/false bool toCheckBoxColumn = true; Object [] Row1 = {... ,toCheckBoxColumn ,... }; Have Fun Never forget it

One of the greatest things about "software engineering" is that you can try out all sorts of strange things and no matter how bad the result is, you're unlikely to do any real damage to anything. Never be afraid to just try; we learn more from our mistakes than from getting it right the first time.

Damn! :doh:

Hi frnd, you have to give the code, So that i can help u...:cool: Nisar Inamdar.

You can attach each field of the datatable with nameofdataset.Tables[0].Rows[i].ItemArray[j] with the indexes i an j changing for the Rows and cells you want to change or read out

It's all or nothing using the standard control. If you wanted more control over the textbox and the list fonts, you'd have to create your own version that supports this, supplying the properties to be set for each side of the control and supplying all the rendering code to draw the textbox and the drop down list. A guide to posting questions on CodeProject[^] Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic      2006, 2007

Or use static class, like class HouseType { HouseType(string){...} string desc; public string Description { get {return desc;}} } static class HouseTypes { static HouseTypes() { type1 = new HouseType("House of type1"); } public HouseType Type1 { get {return type1}} } ... if(myHouse.HouseType == HouseTypes.Type1)... It should have better performance then using attributes but it consumes some extra memory. "Throughout human history, we have been dependent on machines to survive. Fate, it seems, is not without a sense of irony. " - Morpheus "Real men use mspaint for writing code and notepad for designing graphics." - Anna-Jayne Metcalfe

I believe checking form2.IsDisposed will create the functionality that you are looking for, but from reading this thread, it seems like you are inappropriately applying the Singleton pattern if you are needing to perform this check. You might want to read up on your Singleton & Other GoF patterns[^] The Singleton is not really intended for flow control between forms unless it is necessary that (for some reason) you require the EXACT SAME instance of the form throughout the entire application process.(Singletons are more appropriately applied(for example) to concurrent invocation of a state machine on a remote server....or for the Load Balancing example given at the link I included above) Unless you have a very good reason for doing this, then using a Singleton convolutes your logic, and should be avoided. If you are simply wanting to restrict your user to only maintaining one instance of the form at any one time, then you could simply disable the ability to create a separate instance as was demonstrated in previous replies Allow user to instantiate a new form(You're probably wanting it to be Modal) Restrict user from instantiating a second instance of the form User invokes some business logic on the form User closes form when finished If the user wants to replicate the process(let's say...the form allows the user to perform some calculation based upon values selected in an UltraWebGrid), the process would be repeated. Welcome my son...Welcome..to the Machine

SelectedItems returns selected items. SelectedIndices gets selected indexes :)

Thx ill take a look :)

ok, yes that makes sense :)

this would be the best article to explain the same http://www.codeproject.com/cs/miscctrl/RenDataGridComboBoxColumn.asp[^] Keshav Kamat :) India

Certainly you can change the color of each cell in row databound event !!! you can access these information and set the proper color Regards, Jaiprakash M Bankolli jaiprakash.bankolli@gmail.com http://jaiprakash.blog.com/

Well im using delegates to hook up the controller to the UI, this all works fine for me in a simple scenario (one view, one controller). But now im trying to do a more realistic scenario with a couple of forms (mdiparent/childs). As I understand it you typically have one controller for each set of related functionality. Then one controller should be able to handle user input and call methods on different forms?

Model View controller is a set of patterns, and has been implemented in many ways. The main idea behind a MVC is you seperate your view (Screens) from the model (Business Objects) through a center controller. Other patterns can be used here to further abstract the connections, but to keep things simple a good way to accomplish this is to first understand that your screens should know nothing of the business objects. A central controller class is usually constructed to support the "awareness" of the eventing on the view (screens). The controller then wires up to the business objects to do the work. Eventing, Interfaces and sometimes other design patterns are used for this "wiring" of abstraction between the view of the model. For instance, I've just completed a project in which that I implemented a MVC. I added an additional layer of abstraction using a Command pattern. This pattern, when implemented on the Controller and the View, gives a very abstract way of defining actions. Within the view, I constructed CommandAdapters that adapted each of my commands to the controller. The controller also used the commands for communication back to the view. There is alot of debate in the industry on the best ways to create n-tier applications. I've learned that if an application is going through alot of changes, and new enhancements are readily being introduced. Then it is worth the extra time architecting a sound MVC approach. However, if the project is simple, doesn't change much, or there isn't enough funding available. Then using agile development techniques is the better bet. Hope this helps! ~ CodeDoctor ~