Hi Kevin,

#1 I think this is also part of a more general problem. If a user is editing a Date field in the mmDataGrid, but he enters an improperly formatted date then the system fails... this also happens in the jump start web application of the documentation if I enter characters where an integer was expected. How should I deal with this?

#2 I still don't understand how to deal with a failed trigger error. I don't want to check for that in the business rules object, I let the stored procedures deal with that. But should not the business object handle the exception?

Thanks,

Thierry


>>
>>#1 The error in saving data is not related to VFP, the same happens if I make my table a SQL Server table. The error occurs in the line:
>> this.SesBizObj.SaveDataSet(dsSessions);
>
>Gotcha...this is due to the way that character fields are handled in .NET. If you use varchar fields instead, this works like a charm. We're adding a new Trim property to Windows and Web Forms controls in the next release that will handle trimming the extra spaces automatically.
>
>
>>#2 Concerning the failed trigger error, I am not sure I understand what you mean. The failed trigger is a relational integrity trigger.
>
>I was simply stating that a business rule object can be set up to determine whether the data is of the proper range before it ever gets saved.
>
>Regards,