>In the example it is an object based on a class that implements the design pattern.
>I think more of his previous explanation, whenever you create/addobject not from a literal, but a variable, you have already "implemented" a factory pattern, even if the value of the variable is always the same. You could add an if or case clause changing the value and get the "factory" to createobject different items.
>
>In his example he/factory class wraps the act of setting of the string. base class might work by setting cClass value via case, subclass via table, other via hash string or array - so you might have a factory deciding which factory to use as object factory.
>
>

factory = createobject(m.lcSubtype + "_" m.lcFactoryType)

>
>;-)

So your factory depends on a naming convention?