On Feb 1, 2007, at 1:27 PM, Paul McNett wrote:
> Ok, thanks John. This confirms what you said: fields were NULL in the
> backend, they came over as None in Python, Dabo at some level couldn't
> handle it, an error was raised, and the current field values are
> probably something other than None (best guess is the empty
> string). The
> memento would have been filled out in setFieldVal(), and that was
> probably a result of something behind the scenes in Dabo.
Good work!
-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com
_______________________________________________
Post Messages to: Dabo-dev@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
