>>So, I guess, I have to trick IsChanged method for this biz object. E.g. if it's new and empty, I have to return .f., e.g. the object is not changed. So, the record would not be saved.
>
>Well mine similar but hands down when it's a framework that I don't know.
>
>"So, I guess, I have to trick IsChanged method for this biz object. E.g. if it's new and empty, I have to return .f., e.g. the object is not changed. So, the record would not be saved."
>
>Maybe you could do this:
>
>

>scatter fields fieldlistthatusercoudledit name oBlank memo blank
>scatter fields fieldlistthatusercoudledit name oCurrent memo
>lIsChanged = !compobj(oBlank,oCurrent)
>

Cetin

Yes, something like this would work. But basically, I discussed the problem with one of my colleagues and we may want to review and implement this on a generic level. I think, the general rule should be:
if the object is new and empty, don't fire validations and don't fire save.