Ok, that's great. I guess I'll just download it, try Agnes' steps to reproduce and decide for myself. All I was trying to do was not go through all that if I didn't have to. I'll report back here what I find so all the others here will know if it's worth downloading. Would it had been that tough to just give it a try and let us know?

>I can't say yet. But in either case, the desire of the VFPx teams is that users post to the VFPx Discussions or Issue Trackers.
>
>"Issues" get reviewed, assigned, and tracked, and an official status or response will come. Some things reported as bugs are not, and they will get flagged as such after review.
>
>
>
>
>
>>But is this a valid bug? Is there a workaround?
>>
>>>You need to post this in the Issue Tracker on the VFPx website. That is the best place to get a response to this matter.
>>>
>>>http://www.codeplex.com/VFPX/WorkItem/Create.aspx
>>>
>>>
>>>
>>>>High Dough,
>>>>
>>>>today I've tested NewEditPropertyDialog.zip downloaded from codeplex.
>>>>
>>>>It still has the same problems as version 1 with default values (it enters characters only)
>>>>
>>>>Steps to reproduce
>>>>
>>>>open a class
>>>>
>>>>Add a custom prop
>>>>
>>>>set props vaule to .f. (enter in this case) it will alter itself to .F.
>>>>
>>>>
>>>>use your editor rightclicking those prop
>>>>
>>>>enter .f. as default, press Apply
>>>>
>>>>Check the new value, its .f. indicating a character rather then boolean value
>>>>
>>>>close the editor (im keyboard bound but since no button has a shortcut why there is no close button?)
>>>>
>>>>get a reference to the object using sys(1270)
>>>>

loA  = SYS(1270)
>>>>?not loa.yourprop

>>>>
>>>>fails since the value is in chars.
>>>>
>>>>The problem is with the newproperty editor too.
>>>>
>>>>I've created a clone of version 1.0 that deals with the problem for the new dialog. If you like to check it and see if it fits better I can send it to you. Just let me know
>>>>
>>>>HTH
>>>>
>>>>Agnes