>
> > if it's not what Adam says, then I would suspect that the queries of
> the
> > second database is supplying a value for the field in question, while
> the
> > qeries on the first database is not. Both table fields may have a
> default
> > NOW set but only the first db is getting that value since the field is
> > omitted from the query.
>
> This is only an issue for insert statements. update statements do not
> touch fields that no value is supplied for, even if there is a default
> value of now. (Defaults are only ever processed during inserts, and
> only if you do not specifically name the field in your insert
> statement). I am sure the cause will become clear though when they
> investigate a bit further.
>
> Adam
>

that's true - do you know the components he is using? You set select
statements in IBO and IBO creates the insert based on the selected fields,
for you.
Alan