Agnes --

Hey, thanks for the post. Sounds like you have a number of worthwhile features that could be incorporated into PEM Editor. I hope not to force any way of doing things on anybody, and to provide for as many different ways for using it as possible.

First of all, I have indeed lost your "New" form that you sent last year. Can you re-send? I'd love to have a look.

Some comments on your message:

(1) PEM Editor now provides option to ignore _MemberData altogether. I think your suggestion of altering Global values is a great extension.

(2) You were the person who indicated that the values entered for properties were being improperly converted (in many cases, not converted, but left as character). I have tried to fix this, and will make additional corrections if there are any data types not provided for.

(3) You refer to the value editor not meeting your requirements. What are those requirements?

(4) We already have planned an enhancement that will allow customization for setting default values for properties based on their names. A PRG will be provided that can then be modified to suit your own needs (this requires re-compiling the APP, of course)

(5) As it happens, the "grid" part of PEM Editor and the "controls" part are in separate classes. As such, I don't think it should terribly hard to create a mini "New" form (although we have had no plans of doing so.)

(6) You mention over-riding the type ... can you explain?

I'd love to hear from you in more detail.

BTW -- I use PEM Editor now as a replacement for both Property Window and Document View. Yes, there are some features missing ... it's not a complete replacement. Nonetheless, my use of those two has dramatically declined.

>Hi Jim,
>
>this just to the old version I've tested
>
>-modifies _Memberdata without permission.
>--alters value of property to useless value without permission
>
>to the new version, untested but from that what I read from your description. I struggle with Weeesta (censored), there is not much time for anything else.
>I think your editor provides a lot of good functions, but somehow for me it would be fine enough to have the original one with the new button targeting my New form.
>
>Note: Most of the problems below are MY problems bound to MY way to work. I hope this was clear from my last message.
>
>-alters _memberdata. May be set off. No option for global store. I need option Off / _MemberData / Global as optiongroup (on my fingertips)
>-Value editor does not look like it would fullfill my requirements.
>--You chose value on guessing on first letter, I use first for visibility, second for vartype. Others may do different as well.
>--need simple interface for
>---Overide type for special needs
>---Set .NULL. as default
>---set empty (IOW none) value
>-"New" Form seems included. The old version was seperate but easy to mix (If I would have used the editor). I have a "New" form that perfectly works for me and I like to stand with.
>
>I've shiped the "New" form to you last year, that shows how I deal with _Memberdata,visibility and valuetype problem. (If this missed you, just post here. We can discuss my ideas on this example?)
>
>My idea about it was to have the interface I use in the new form or the edit to keep it strait (same container class for editor and new forms) For me New is much more important then Edit. This works, so its fine.
>
>Agnes