fractional truncation message

Using SQL 7 with an Access 2000 MDB front end with ODBC linked tables.

Have a DateModified field which previously was smalldatetime. Changed over
the weekend to datetime. Field is updated with a trigger that sets value to
GetDate().

One record in the table now cannot be updated. In Access, get message:

[microsoft][odbc sql server driver]fractional truncation (#0)
[microsoft][odbc sql server driver]timeout expired (#0)

In QA (using Update), no message; just hangs.

Note that many records in the table have been modified since the change, and
there doesn't seem to be a problem. It just seems to be this one record
(possible others that we haven't come across yet) that will not allow
updates.

Any ideas how to resolve this?

Thanks!

Neil

Re: fractional truncation message

Forgot to note in the below:

* The Update query I'm running in QA just sets a field value to it's current
value -- i.e., Update MyTable Set Field1=100 Where PKID=12345. In other
words, not touching that date modified field at all.

* I tried copying the record to a new record. The new record, with all the
same data, works fine, and allows the update.

Thus, I'm concluding that this one record got corrupted somehow when I was
modifying the field type. How can I resolve without recreating the record
(or is that the only way)?

Thanks!



"Neil" wrote in message
news:DTV9j.228$se5.71@nlpi069.nbdc.sbc.com...
> Using SQL 7 with an Access 2000 MDB front end with ODBC linked tables.
>
> Have a DateModified field which previously was smalldatetime. Changed over
> the weekend to datetime. Field is updated with a trigger that sets value
> to GetDate().
>
> One record in the table now cannot be updated. In Access, get message:
>
> [microsoft][odbc sql server driver]fractional truncation (#0)
> [microsoft][odbc sql server driver]timeout expired (#0)
>
> In QA (using Update), no message; just hangs.
>
> Note that many records in the table have been modified since the change,
> and there doesn't seem to be a problem. It just seems to be this one
> record (possible others that we haven't come across yet) that will not
> allow updates.
>
> Any ideas how to resolve this?
>
> Thanks!
>
> Neil
>