how to transfer data from one data grid view to another data grid view in c#


 

how to transfer data from one data grid view to another data grid view in c# 

Data Grid

 

DataGridView control accessible as a piece of Windows Forms controls in Visual Studio 2008 is significantly more impressive than it’s past adaptations. This instructional exercise is an essential acquaintance of how with compose a straightforward information driven application utilizing Visual Studio 2008 wizards without composing a solitary line of code. In my next articles, I will discuss more point by point highlights of the DataGridView control.

The DataGridView control gives an amazing and adaptable approach to show information in an even configuration. You can utilize the DataGridView control to show read-just perspectives on a modest quantity of information, or you can scale it to show editable perspectives on extremely huge arrangements of information. This control additionally we should you show information in an ace subtleties see.

With the DataGridView control, you can show and alter even information from various sorts of information sources. Restricting information to the DataGridView control is clear and natural, and by and large it is as basic as setting the DataSource property. At the point when you tie to an information source that contains different records or tables, set the DataMember property to a string that indicates the rundown or table to tie to.

The DataGridView control underpins the standard Windows Forms information restricting model, so it will tie to examples of classes portrayed in the accompanying rundown,

Any class that actualizes the IList interface, including one-dimensional exhibits.

Any class that actualizes the IListSource interface, for example, the DataTable and DataSet classes.

Any class that executes the IBindingList interface, for example, the BindingList<(Of <(T>)>) class.

Any class that executes the IBindingListView interface, for example, the BindingSource class.

The DataGridView control underpins information officially to the open properties of the articles returned by these interfaces or to the properties assortment returned by an ICustomTypeDescriptor interface, whenever executed on the brought protests back. Regularly, you will tie to a BindingSource part and tie the BindingSource segment to another information source or populate it with business objects. The BindingSource segment is the favored information source since it can tie to a wide assortment of information sources and can resolve numerous information restricting issues naturally.

Have any Question or Comment?

Leave a Reply

Your email address will not be published. Required fields are marked *

Categories

%d bloggers like this: