Fractionaltruncation on form save (1 Viewer)

[jaydwest]

I have an MS Access Application (originally MSA2003 but now MSA2007) with a SQL Server Backend (SS2008). I created a simple entry form based on a table in the SS. It is based on a single table. There are several date fields and two memo fields (SS = varchar(2000) each). There are three drop down lists on the page, one lookups data in a large table (mucho records).

Intermittently, and still unpredictably, the page locks up when it is saved. It will work for a while and then locks up. After it locks up on a save, it will continue to lock up. The error messages are:

FractionalTruncation(#0)
Query timeoout expired (#0)

There are two users using the form. One claims he can use it with no problem, the other cannot. I do not think it is a contention issue because I can test it in the middle of the night on a weekend and I get the same message. The page locks are set to edited records.

In earlier research there were some posts about using smalldatetime fields. I resolved that by changing all date fields to full datetime fields.

This is a total mystery to me so far. Has anyone had experience with this problem or does anyone have a suggestion on how to troubleshoot this issue?

 

[boblarson]

Which SQL Server ODBC driver are you using?

 

[jaydwest]

SQL Server. Don't know what file name is. If I need it, where do I look?

 

[jaydwest]

Found it

SQLSRV32.DLL
Version 6.01.7600.1638
07/13/2009

Thanks for your help

 

[boblarson]

Found it

SQLSRV32.DLL
Version 6.01.7600.1638
07/13/2009

Thanks for your help

Actually I was just wanting the name of the odbc driver you chose when setting up the DSN. Was it:

SQL Server
or
SQL Server Native Client
or
SQL Server Native Client 10

 

[jaydwest]

I found the problem. It turned out that MSA did not like two memo fields in a record. The memo fields were linked to a SS2008 Database with two varchar(2000) fields. Both the record size conformed to MSA and SS limits. When I changed the varchar(2000) fields to varchar(1000) fields, the problem was resolved.

SURPRISING HUGH!

 

[boblarson]

Not surprising. I've had some issues similar with a SQL Server 2005 TEXT field datatype which we ended up having to change to VarChar(500) in order for us to not get an ODBC error.