>>The session class was designed to be lightest weight (smallest memory footpirnt) of all VFP base objects. I'm just speculating that the decision not to include a visual designer may have been based on this spec.
>>
>>Anyway, glad you got back to me because I just stumbled across an article in the Oct issue of FPA that discusses to how convert custom class objects to session class objects, giving you the best of both worlds.
>>
>>Charlie
>
>The Fox team has given a couple of reasons why the session class is code only:
>
>- It's designed for middle tier COM servers, which don't have any UI
>- Because there is no visual designer, it is light-weight
>
>In VFP7, the session class has been changed. All native methods are PRIVATE by default and won't be visible under COM. This may change what Larry said.

I think that what Evan is trying to say (and I partially agree with this) is that a designer is, for the most part, only a 'class parser'. Like in VB- a Class module is only text code, but you can navigate through the methods with a combo box that holds all the available methods, and you can set properties in a property sheet. I don't think that we would need any modifications to the Session or any other class to get this, we would only need a designer that is capable of handling prg classes.