StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13929065
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-12-18T08:32:57.183
FavoriteCount
0
LastActivityDate
2012-12-18T09:24:03.883
LastEditDate
2012-12-18T09:24:03.883
LastEditorUserId
1185136
OwnerUserId
1185136
ParentId
13928713
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
You can declare the object you want to share as a <a href="http://msdn.microsoft.com/en-us/library/79b3xss3%28v=vs.80%29.aspx" rel="nofollow">static</a> field: <pre><code>public partial class Form1 : Form { public static object MyObject; //... } </code></pre> ...or declare it as a static property: <pre><code>public partial class Form1 : Form { private static object obj; public static object MyObject { get { return obj; } // read-only } //... } </code></pre> ...and then you access it like this (in other classes): <pre><code>object obj = Form1.MyObject; </code></pre> However, if you have multiple instances of Form1, MyObject will be the same for all instances of Form1. <hr> Another approach is setting the <a href="http://msdn.microsoft.com/en-us/library/system.windows.forms.form.owner.aspx" rel="nofollow">Form.Owner</a> property, by calling <a href="http://msdn.microsoft.com/en-us/library/szcefbbd.aspx" rel="nofollow">Form.Show()</a>: <pre><code>public partial class Form1 : Form { public object MyObject; // no static required public Form1() { InitializeComponent(); Form2 f2 = new Form2(); f2.Show(this); // this sets the Form.Owner property on f2 } //... } </code></pre> ...and then you access it like this (in Form2): <pre><code>Form1 f1 = (Form1)this.Owner; object o = f1.MyObject; </code></pre> The advantage here is that you can now access all public members of Form1, even though they are not declared static. But if you minimize/close Form1, Form2 will also be minimized/closed. <hr> If you don't want to use static or Form.Owner, you can also pass a reference to Form1 instance as a parameter. For example, in Form2 you can write a constructor that takes Form1 as a parameter: <pre><code>public partial class Form2 : Form { public Form2(Form1 f1) { InitializeComponent(); object o = f1.MyObject; // access MyObject like this } //... } </code></pre> ...and instantiate Form2 like this (in Form1): <pre><code>Form2 f2 = new Form2(this); </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POShare object instance between multiple forms
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USRudey
UserOwnerUserId
1. USRudey
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POShare object instance between multiple forms
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.