>I don't disagree with anything you've said. But, neither does it gainsay my original comment
>
> "the data layer has to be done its way only - or funny things happen ..." .
>
>FWIW I started looking around for a different framework because Codebook - which I have been using for years and am very used to - appears to be at a dead end in both its open source and MM variants. Codemine seemed (still seems <g>) to be the best of the alternatives on offer, but compared to CB I do find its data paradigm totally different and all the stuff that gives it its good data capability does bring with it a lot of baggage ...
>
>Cheers
>
>Brian Abbott
>
>
>
>>>>I think Codemine's data layer is its *best* feature.
>>>
>>>yes, I agree its very good - _as long as_ you do it the CM way ;-)
>>
>>OK. But isn't this why you buy into the framework?
>>
>>>use a control's Valid instead of afterchange/validatefield

Brian,

Agree with you, but only partially. Because I am trying to reuse code from a FPDos application I don't do everything the Codemine way. For example, I use native REPLACEs, etc without serious consequences. Yes, you give up some automatic behavior, but not all.

Alex