Herfried,
In regard to why I am declaring structures within my class.....
I have a dataset that has 4 records. The fields in the dataset are like,
Year1, Year2, Residual (decimal values)
For each of the records in the dataset, they are of a specific type, like
one row is the principal, the next row is the interest etc.
So, I thought to create a class that has 4 types, each of the types would
have the same properties , but I would be able to distinguish which type the
Year1 field was associated with.
I could then create a single instance of the class and then associate the 4
types with the individual dataset rows. Might not make much sense, I'm open
to suggestions.
Yes, the naming convention is ugly...have you seen the new suggested naming
conventions from Microsoft for .Net...I actually prefer something like m_int
or m_obj....but I'm dealing with the type of client that insist on running
FxCop and complaining about any warnings.
STom
"Herfried K. Wagner [MVP]" <hi***************@gmx.at> wrote in message
news:bv************@ID-208219.news.uni-berlin.de...
* "STom" <st***********@hotmail.com> scripsit: I have a class declare like this:
<Serializable>Public Class Talk
Public Structure _localTalk
Public _iTalkNumber as Integer
End structure
End Class
I can see the structure from other classes, but I cannot see the
internal data member. I've also tried setting the internal data member to private
and created a public property, but I couldn't see that either.
The data member is part of the structure. You will have to create a
public property of type '_localTask' (ugly naming convention!). Why do
you declare the structure inside the class?
--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>