I am running VB5.0 on Windows 95 & accessing a Sqlserver 6.5 database using
an ODBCDirect type connection. Further, I have set 'defaultcursordriver'
to 'dbuseServerCursor'. The application is a non-visual 'batch' program
which does database I/O's & performs some updates on the database.

The executable runs fine & performs the expected database updates but right
at the end, gives a messagebox saying 'invalid page fault in module
kernel32.dll'.
When I run the application thru the development environment (thru the
de{*filter*}), it also goes to successful completion BUT gives the same error
when I  try to close VB.

T3501001 caused an invalid page fault in
module KERNEL32.DLL at 014f:bff9a08c.
Registers:
EAX=0063fc1c CS=014f EIP=bff9a08c EFLGS=00000246
EBX=815cb1e4 SS=0157 ESP=0063fc18 EBP=0063fc6c
ECX=00000157 DS=0157 ESI=00000000 FS=3d5f
EDX=0063fe28 ES=0157 EDI=10a00000 GS=0000
Bytes at CS:EIP:
5e 8b e5 5d c2 10 00 64 a1 00 00 00 00 55 8b ec
Stack dump:
815cb1e4 c0000005 00000001 00000000 bff9a08c 00000000 00000000 030a0000
00000001 0063fc30 0063fe28 030a6bd1 00000000 00000001 030b82e3 030a0000

Another weird thing about this is that it does not happen on all machines -
works on some & fails on some. The machines I have tested with are all
P-166 MHz or higher & all have 32 MB of RAM or more & have Windows 95 as
their O/S. I have not been able to find any pattern to isolate the problem
except that it works fine when I DO NOT set the 'defaultcursordriver'  to
'dbuseServerCursor'.  

I have also installed Service Pack 3 but to no avail. I also downloaded an
updated version of kernel32.dll from the microsoft support page but that
hasnt helped either.

Has anyone seen or heard about this problem ?? Any thoughts or suggestions
are most welcome.

Thanks!

Shireesh Khandkar

I had a similar problem using VB5 and Crystal Reports 4.6 that shipped with
VB.  It seems that I would get the IPF in Kernel32 if I made an ODBC
connection AND used the Crystal Report control in the same session of the
program.  If either operation was left out, I did *not* get the page fault.
 I searched the internet over and did not find an answer.  It went away,
though, when I upgraded Crystal Reports to 5.x.

Hope this helps at least a little...
Phillip Koebbe
Eagle-Picher Technologies, LLC