Printable View
I am a newbie and self teaching and have a general question about a class or an object. I have an item (Component) that has over 600 items that are associated with it. Would it be wise to create an Object of a component and define all of the associated items within it?
What are the benefits of doing this?
Can you explain more spcifically what do you mean by items + component !!
Pirate,
I have an item (a component, electronic component), each one has over 600 different entities that are used to describe/define it.
Does that make more sense?
Here is some other info that may help. Currently, the info used to describe a particular "Component" is contained in Paradox tables. I am writting an app that will access that data, populate the tables with new info, edit what is currently there, etc. I am currently not using a Class or an Object in the app, would it be better if I was to use one?
Classes can encapsulate your objects to look like one big object.Besides , VB.NET lets you inherits from base classes and enhances the nested classes with additional methods.
you have to read more about OOP in VS.NET so that you be familier with such concepts .