Hi Al,

>Adding a call to DisplayErrors works. I like working exclusively with the entities and I thought it would be nice if the SaveEntity method would complete the cycle. But for now, I'll probably stick with the page Save method.
>
Your welcome, glad you got it going. Remember though that displaying a message to the user is a UI thing and not a business object task. That is why the DisplayError is written in the base for the page class. Also, a business object or entity should not know anything about your UI implementation. I suppose it would be possible for Kevin to raise an event at the business level to notify any subscribers (UI) that a business rule was broken, but in this case the pages Save() is there for that purpose.
Tim