It is well documented on the net that oleaut32.dll and vb32 are not fully
compatible. oleaut32.dll comes with ms office 97, MS Internet Explorer 3.0
etc.  
In my problem, Code (Using Recordset object) which has previously worked
with vb4 now fails producing message:

VB32 caused an invalid page fault in
module OLEAUT32.DLL at 0137:65346a23.
Registers:
EAX=00620de4 CS=0137 EIP=65346a23 EFLGS=00010246
EBX=01326038 SS=013f ESP=0074f5d0 EBP=0074f8e8
ECX=0000000f DS=013f ESI=0000002e FS=0d8f
EDX=00000002 ES=013f EDI=0074f840 GS=0000
Bytes at CS:EIP:
8b 3e 03 fa 03 f9 f7 d1 83 c7 04 23 f9 8b c8 57
Stack dump:
0074f840 0137614c 0fb3e439 0fb3868b 00000032 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

This error occurs consistently in VB4(32) but not in compiled EXE file.

oleaut32.dll version 2.20.4054
olepro32.dll version 5.0.5055

Despite the series of correspondence on newsgroups (cf Carl and Gary's
Microsoft News Database http://www.*-*-*.com/ ),
there appears not to be a solution - certainly not from microsoft KB

Has anybody found a solution other than uninstalling MS Word and Internet
Explorer 3.0 from the PC
--
Peter J Fay
KIRKWALL Orkney

44 1856 875387
44 1856 870043 FAX

Did you run Regclean?  May be the sequence of installing W32 apps makes a
difference (VB4.0 installed on top of the stack).  As a last resort if
nothing else works, reinstall Win95, VB4.0 and the rest.  Apparently
problems could come from many sources like upgrades, new installs.

If MS Word and IE3.0 uninstalled fixes your problem, then the difference in
states between (VB4.0 & MS Word & IE3.0 installed) and (VB4.0 & less [MS
Word & IE3.0] installed) is the problem/solution.  To get to the root of
trouble, if there would be an easy way to track and record changes in the
Registry settings and changes in OS components catalogue or versions of all
relevant system files in the two instances, then that difference would
point to the flaw.

The two instances being:  1) when you have MS Word & IE3.0 installed, and
2) when they are uninstalled.  The recorded difference would tell where the
flaw was introduced.  This recorded difference would consist of: new
versions of old OS files, new OS files/patches, different registry
settings.  There would be some 'candidate' differences that that would be
harmless.  But one or more difference(s) would certainly be the one(s) that
did cause the problem.   (To make a program do this automatically sounds
like a good shareware project.;)

I also had trouble with OLEAUT32.DLL.  My VB4.0 was paralyzed by the error
message: "VB32 caused a stack fault in module OLEAUT32.DLL at
0137:65356ebe" when I tried to open References from Tools menu in VB4.0.
I had a few software upgrades and installs lately.  Suspected that my
registry was in err, I tried to run Regclean, but was blocked by an almost
identical message: "Regclean caused a stack fault in OLEAUT32.DLL at
0137:6535ebe"

Then I uninstalled most of my apps one by one.   And when noting helped, I
uninstalled Win95, then reinstalled Win95, VB4.0, etc., less excess
baggage.  Now they all work fine.

Being only a hobby programmer, I don't use OLE automation every day in
VB4.0, and I don't know exactly which app spoiled my registry.  Just like
in your case, my VB4.0 worked fine before.  I can not prove the reason for
my OLEAUT32.DLL problem.  Just only guess that because W32 apps liberally
use the registry, and install their own brand of  *.DLLs, etc, perhaps here
is where the trouble comes from.  Under some circumstances OLEAUT32.DLL can
not to 'talk' to other OS family components because of wrong module version
is registered/overwritten during upgrades and installs.

Curious to now how did you solve your problem.
Regards,
Endre