Hi Larry,

>>Ah... you mean like .Top, .Left, .Width, .Height etc propeties. However would adding just these few properties significantly reduce lighweightness ?? I don't know. It would be nice if we can get some info from the VFP team what the reason behind this issue is.
>
>Actually, it's more than that. The Class Designer presets some information that isn't done in PRG code. Not only dimesion information, but things like Count for pageframes, commandgroups and optiongroups as well as other things that add to overall memory footprint when instantiated.

Well these are differences, but personally I doubt if this has anything to do with memory footprint. I think it is in what you define lightweightness. You cannot define nested containerships in PRG's but to my knowledge its because of shortcommings in the VFP language but does not have anything to do with memory footprint.

>It may take more effort than considered profitable to change the way the Class Designer handles things like Session when PRGs are a viable solution now.

I don't know for session, but for exmaple: I store gridheaders in my VCX files too. I use them in forms directly (Not by deleting old headers and adding the new one). I don't see why it should not be possible to visually edit a gridheader. When it comes to the other classes I cant see why cursors, relations, dataenvironment can be contained in forms, but cannot be cointained in visual class libraries.

I can't see why this should be so different with a session class. Can't it be compared with a custom class, but only holding its own datasession ??

Walter,