Thank you very much for that information, the required flag for the
ORDDATEField had not reset to false.

I would of never of thought of looking there.Probably when I reset the
fields from not null to nulls.

thanks
Daniel

>Is the field flagged as Required=True somewhere in your code or field
>properties in the DFM? If you are using persistent fields, it might be
>there. A property does exist for a persistent field to say that it is
>required, even if it's not defined as such at the database level. This
>happened to me before, especially when a field was defined as not null in
>the database then changed to allow nulls, but the property Required in the
>persistent fields was still set to True. I had to manually change them to
>False. I know that this is one area of the code that you might not think
>of looking at, I know I didn't at the time, it took me a few days to figure
>it out.
>
>Hope this helps.
>
>
>Daniel Rail
>Senior System Engineer
>ACCRA Group Inc. (www.accra.ca)
>ACCRA Med Software Inc. (www.accramed.ca)
>
>
>Yahoo! Groups Sponsor
>ADVERTISEMENT
><http://rd.yahoo.com/M=215002.1818248.3328688.1261774/D=egroupweb/S=1705115386:HM/A=847665/R=0/*http://ads.x10.com/?bHlhaG9vbW9uc3RlcjcuZGF0=1016820650%3eM=215002.1818248.3328688.1261774/D=egroupweb/S=1705115386:HM/A=847665/R=1>144d255.jpg
>144d30a.jpg
>
>To unsubscribe from this group, send an email to:
>ib-support-unsubscribe@egroups.com
>
>
>
>Your use of Yahoo! Groups is subject to the
><http://docs.yahoo.com/info/terms/>Yahoo! Terms of Service.

[Non-text portions of this message have been removed]