|
|
Posted by Neil on 12/19/07 07:01
"Erland Sommarskog" <esquel@sommarskog.se> wrote in message
news:Xns9A0AEDA372B21Yazorman@127.0.0.1...
> Neil (nospam@nospam.net) writes:
>> 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)
>
> Note that these errors are from ODBC SQL Server driver, not from
> SQL Server.
>
>> In QA (using Update), no message; just hangs.
>
> Did you close down the Access application? While hanging in QA is
> consistent with he "timeout expired" in Access (QA does not have
> any timeout by default), my suspicion is that the first error
> left the row lock and blocked.
>
> You can use sp_who2 to determine if you have any blocking. If there a
> non-zero value in the Blk column, that is the spid of the blocker.
> Examine further to see which application it's running.
>
>
Yeah, you were right. I just tried it, now while everyone's out of the
database, and it updated fine. I also downloaded a backup to my development
machine, and it was fine there too.
The reason I thought it was corrupted was because, from what I read, the
"fractional truncation" message has to do with date/time fields. And since I
had just changed the datemodified field from smalldatetime to datetime over
the weekend, it seemed like too much of a coincidence that this error had
nothing to do with that, especially since I've never seen this error before
in all the years that we've had this configuration (about 7 years). So there
definitely seemed to be a correlation.
Neil
Navigation:
[Reply to this message]
|