Hi again,
I am referring an earlier question here trying to enlarge upon the concept I
am pursuing.:
Each object is a subassembly. They are all significantly different in
detail and content but are all derived from an abstract subassembly class.
An assembly is defined as a tree of subassemblies. There are multiple
levels of subassemblies that can be assembled in many different
configurations. Someone on the production floor can open an assembly object
and request information regarding that particular object. One subassembly
requested method (among many) would be a list of subassembles within that
object.
If required, a subassembly can be be selected and displayed via a method
specified in the abstract class definition. What I want to do is direct the
subassembly to display itself as a form on the CRT. So, what I want to do
is build into each of these subassembly objects a form method to display its
content. I want the form to exist within the subassembly although the
subassembly, itself, is not a form.
It would be much easier to maintain such a system if I could use the VS form
designed capabilities (as oppopsed to dynamically building a form within the
assembly). So, the sequence would be as follows:
1, Open Assembly
2. Display subassemblies
3. Select subassembly
4. Direct subassembly to display itself
5. Display subassemblies
6. Select subassembly
7. Direct subassembly to display itself
8. ...
This can be repeated to 'n' levels of subassembly.
A sloppy method but equivalent method (IMHO) would be to create a form
application for each subassembly which would be fired off by the subassembly
object when a request is made with the invocation providing the necessary
data retrieval information. I do not like this. I want to find a method
that I can use to include this display mechanism in each subassembly object,
thus encapsulating everything within a subassembly to one inclusive object.
Thanx all,
Happy Ramahanakwasmas
WEB