David,

Ah, I like this one a lot.

Am I interpreting this correctly : I wrote a form class which fires up all
my forms, keeps track of them, hides them, releases them, etc... It works, however the problem I have found with it is that it is a PRG which I keep
keep in a procedure file, along with other custom classes, and there is no
VISUAL way of me to look up the class's methods, properties, etc... Each time
I have to open up the PRG and scroll through the doc or code to work them
out, or print it.

If I understand it correctly, the beauty of what you describe is that
I could implement my Form Manager class through a container where each of the
class's methods are methods of the container. This way, any time I want to
look up what methods or properties are available, I can do it visually
and much more quickly and efficiently through the Form Designer or Class Designer.

In fact I could convert the whole of my procedure file classes to
methods of a container, particularly if most of those classes are likely to be
used in most applications ?

Is that what you were describing ?

Michel.

================ Original message follows ====================

>Michel,
>
>To add to the others. The container is also used to create reuseable components where you have to group more than one kind of other objects together. For example I have a cntMAPI class inside it are a MAPISession, MAPIMessages and a txtStatus. The container has the methods that the client form uses to talk to the contained objects. It also provides a higher level of abstraction of the interface.
>
>>I am not sure as to what sort of applications the CONTAINER and
>>SEPARATOR classes could be used for.
>>
>>I would be interested in hearing about how others have used
>>those two classes to good effect.