>>>Can you please elaborate more on your approach?
>>
>>(1) I never use grids for data entry, so I have not tried to implement it in a grid.
>>(2) I have not tried instantiating it on the fly.
>>
>>Basic VFE tiers include cursor, data environment, business object, presentation object and form, and
>>I've just been dropping instances of the class on the presentation object (which is a container) as needed --
>>i.e., one for each numeric textbox on the PO. For each instance, I simply set a cAssociatedControl prop to the name of
>>the numeric textbox that gets updated.
>>
>>Because I've coded the class to work with the (modified) way I do things in the VFE context (and it is a sub-sub-class of
>>VFE's default textbox control), the code would not be straightforwardly transferable even to someone else using VFE.
>>But I can certainly pull together a description of the relevant PEMs and some code snippets if you really think they
>>would be useful to you.
>>
>>-m.
>
>What I think we may want for the grid (and it's a bit unfortunate) is to use a writable cursor/CA/View with character fields instead of numeric and do a replacement with the values behind the scenes.
>
>I was originally thinking of trying to create a textbox class that will instantiate a different class when user tries to type something, but I believe it would be too complex (for us) to design such a class and adjusting grids, though would require some re-design, may be easier.

My character textbox counts on the associated numeric (hidden) control being there. It uses the InputMask of the numeric control to set its own mask on the fly.