Definitely Kevin, we need that, is like in vfp with remote views, any rule a odbc error arises, and let option of going to the textbox and complete and try to save again (if it is null etc for example) or issue a tablerevert() for the view..


Do we have to wait for the next version ? what approach can be used now in terms of try catch ?

Thanks again

Regards

Norman





>Norman,
>
>>What does it has to be done in order not to quit the app. for this kind of errors. for example if a DB rule is broken, just advice the error, and wait user to cancel the saving or he will still get the same error ther is no option.
>
>Although there are definitely errors that you want the application to shut down when encountered, I'll be making it easier in the next version of MM .NET to simply display some errors and continue.
>
>Regards,