Hi!

Well, the explanation is simple - it SAVES it correctly (just look to the properties memo in VCX opened as DBF), but is not able to load it. This is because it loads properties using syntax "{objname}.{propname}". When {objname} is default name generated using class name on the fly when members added to container object, all is ok. When {objname} is something different, it just does not exists...!!!

I see how it could be solved though. In properties memo store properties in following way (Assume "cb" is a class name of command button)

cb1.name="cbspecial"
cbspecial.width=128
...

In above way VFP first changes the default name of member to special name, then load all the rest properties.

I think this should be reported to MS as a bug. Would you allow me to do this?

>Hi Folks...
>
>I'm sharing some problems that I found in VFP 8 here... Is it the right place?
>
>Well, try it:
>
>1) Create a class (CommandButton) and change some properties.
>2) Create a class (CommandGroup) and set MemberClass = Class_CommandButton (step 1) - and Change some properties (Height / Width / Top / etc) in that class...
>3) Now, save it!
>4) Open it! ... All is right. Change the name of one button. Save.
>5) Open again... Your properties are wrong now... It respects the values sets on step 1...
>
>VFP 8 is the best tool that I have seen. ;-)
>
>[]s!