In investigating this I also came across the problem
that a 
numeric field set to 0 when that is the very first
edit to that 
numeric field will not be displayed when 
called as:

    <td 
tal:content="structure 
python:context.workingorder.field(size=5)">
      
startdate</td>

I set this to 0, it never makes it through the 
system.
I get an "ok_message=" in the URL, and no auditors 
fire.
If I set it to some none-zero value say 9, commit it (I 
see
that workingorder has been edited in the 
returned
message, and I see output from the auditors) and 
then
change it to 0, it works fine.

-- rouilj

Logged In: YES 
user_id=6405

Added unit tests for this case, tested the interface. 
 
Works for me... 
 

Logged In: YES 
user_id=707416

What back end did you use? I use anydbm or bsddb.

Logged In: YES 
user_id=6405

The unit test I wrote (for the cgi form parsing) is backend-agnostic.

I've just added another test in the db to check the setting of 0 values there. Both anydbm and bsddb pass the test. I can't think where else this could be going wrong. Can you set the value to 0 using the roundup-admin interface? How about the mailgw?