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) and
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. (Occasionally printing will generate a spool32.dll page
fault and previewing will generate an Unknown page fault with the same
address information.)
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. Single page reports print/preview just fine. The
error only occurs when 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 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) and
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. (Occasionally printing will generate a spool32.dll page
fault and previewing will generate an Unknown page fault with the same
address information.)
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. Single page reports print/preview just fine. The
error only occurs when 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 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