Hi,

Case: when closing a windows form, we check for dirty objects by using
Session.IsDirty() (we use session per form). When a new object has
been added, and not yet saved to the session, the IsDirty call issues
a select to get a new Id for the object (we use hilo generator). The
Id that gets assigned to the object causes problems because in a later
stage we use Id 0 to check if the object is new.
Does anyone know if this is by design or that it can be avoided some
way?

Thanks in advance,
Hans

-- 
You received this message because you are subscribed to the Google Groups 
"nhusers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/nhusers?hl=en.

Reply via email to