That's the start of writing accessors in C#, which you can refer to
https://msdn.microsoft.com/en-us/library/aa287786(v=vs.71).aspx if you need more information.
Now having this is not enough to achieve what you want, but this is the start.
Question is where would be the best place to declare your data structure to contain data ? Surely our C# program must have a starting Class with the Main method right ?
Your Windows Forms are just UI diagloues to interact with your user. At the end of the day, you need to visualise that the Main Class is where one would encapsulate the entirety of the Application you are designing
So if you feel the data belongs to the whole program, then declare your array inside the Main Class.
However if you feel that piece of data should belongs to ANOTHER CLASS because another class is playing the role of providing functionality to that piece of data, you should declare it in the other class
Think of Class as an Organisation, as a Person, as a Container, as a Group. In layman, your Family is one big Class, but you are another Class, your Mother is another Class and your Father is another Class. That's one possible way to organising things.
So your Father assuming is the breadwinner earn his salary and then he store this salary with him. He then decided to dedicate a portion of his salary to the Family and hence transfer a portion of this salary to the Family Class. Now your mother require the money for daily household expenses and took a portion into her own Class for storing. And she then assign you another portion out of her own for your daily expenses.
So while the money comes from your Father, surely when you consider how the flow of data and responsibility works, it get scatter all over the different Classes.
Of course, your Father can also when he collected his salary store immediately into the Family class and he does not have the functionality of storing the money himself. So when he need some money, he just draw from the Family Class, which act like a bank to him.
If your Father is a henpeck(nicely put as respect his wife), he might need to use your Mother's functionality to retrieve money because he is only exposed to the SET accessor to put money into the Family, but no GET accessor is made available to him. The only GET accessor to the money in the Family Class is via your Mother's drawMoney method.
This is a very very simplistic manner to look at Classes because it gets more complicated once you put Objects into the whole conversation. But I just want you to think how do you structure your data into which Class responsibility. Thats the whole idea of Object Oriented Design.
Next is if you are at liberality of using better containers, read up on
https://msdn.microsoft.com/en-us/library/ybcx56wz.aspx, and these any of these functionalities to manage your data instead of a simple minded Array. Not that Array is not the right way, but it is a lower level data structure which requires more work to define functionalities around it for CRUD operations.