R
Ron Kunce
I have a fairly complex system using an Access 2000 .adp from an SQL Server
7 database, which is used across the state by several hundred users. I
have
encountered a recent problem with a couple of reports which have been
running unhindered for several years. However, when our tech services
section began putting in a few faster PC's (450 MHZ + Pentium 4's) while
retaining the Windows 95 OS, these two report began generating MSAccess
Page
Faults in Kernel32.dll at address D16F:. . . and crashing the session on
these newer PC's.
The weird thing about them is, it only causes the error when previewing or
printing records from which the detail section must format/print a second
(continuation) page based on the size of the SQL Server text field. Single
page reports print/preview just fine. The
error only occurs when the size of the text field causes the
printing/previewing the second page. Our Tech
Services believe it has to be the application code. However, I have
eliminated all code on the report as the cause, and I still get the same
error on these machines. It has to some kind of conflict between Access
2000 and Window 95 on these faster processors. But where and is it
correctable? (Windows NT and 2000 PC's continue to work fine.)
I understand that in VB it is sometimes necessary to retrieve the text field
data in chunks using the fld.GetChunk(ChunkSize) function. However,
according to the Knowledge base article, this is for fields containing more
than 4000 characters (8000 bytes with two-byte character i.e. unicode).
Since this problem is occurring before the size gets to 1000 characters, I
don't believe the GetChunk() will work.
I have searched the web and google groups for answers and can't seem to
find anything even remotely close. Does anyone have any ideas?
Ron Kunce
7 database, which is used across the state by several hundred users. I
have
encountered a recent problem with a couple of reports which have been
running unhindered for several years. However, when our tech services
section began putting in a few faster PC's (450 MHZ + Pentium 4's) while
retaining the Windows 95 OS, these two report began generating MSAccess
Page
Faults in Kernel32.dll at address D16F:. . . and crashing the session on
these newer PC's.
The weird thing about them is, it only causes the error when previewing or
printing records from which the detail section must format/print a second
(continuation) page based on the size of the SQL Server text field. Single
page reports print/preview just fine. The
error only occurs when the size of the text field causes the
printing/previewing the second page. Our Tech
Services believe it has to be the application code. However, I have
eliminated all code on the report as the cause, and I still get the same
error on these machines. It has to some kind of conflict between Access
2000 and Window 95 on these faster processors. But where and is it
correctable? (Windows NT and 2000 PC's continue to work fine.)
I understand that in VB it is sometimes necessary to retrieve the text field
data in chunks using the fld.GetChunk(ChunkSize) function. However,
according to the Knowledge base article, this is for fields containing more
than 4000 characters (8000 bytes with two-byte character i.e. unicode).
Since this problem is occurring before the size gets to 1000 characters, I
don't believe the GetChunk() will work.
I have searched the web and google groups for answers and can't seem to
find anything even remotely close. Does anyone have any ideas?
Ron Kunce