Visual Basic, ctl3dv2.dll * MS-Office = CRASH!!!

N
#1 / 4

ctl3dv2.dll * MS-Office = CRASH!!!

[code to use ctrl3dv2]

Quote:

>Now, everything works fine at runtime. But if I try to run the software
>while MS-Office is running (the icons are up there in the corner, none of
>the software has to necessarily run) then in a matter of time (sometimes 3
>seconds, sometimes 30 seconds) MS-Office crashes with

>"MSOFFICE caused a stack fault in Module USER.EXE at 0001:808A"

assuming everything is declared right try this:

since ctrl3dv2 only afftect VB common dialogs, and message/input boxes
write wrappre functions for each of these

i.e. in the function
1) register with ctrl3dv2
2) call messagebox/inputbox/cmdialog
3) unregister

I had problems along the same line until I decided to do it this way. The
time to register and unregister is very very rarely noticible....

NV

Sun, 03 Aug 1997 07:36:00 GMT

Peter G. Milla
#2 / 4

ctl3dv2.dll * MS-Office = CRASH!!!

Beware of leaving the DLL registered. I was getting all of these GPF's
during design mode, until I changed my method of implementing 3d
dialogs.

What I do now (and haven't gotten a single GPF w/ lot's of other
programs running) is to register the DLL, the Call the Dialog, the
unregister the dialog. Something like...

rc% = Set3d(0) ' custom function to register DLL
CMDialog1.Action = 2 ' Call Common Dialog
rc% = Set3d(1) ' custom function to deregister DLL

This may eliminate your problems.

--
----------------------------------------------------------------------------
Peter G. Millard //////////////// "Error reading Drive A:

Co-Maintainer of comp.lang.basic.visual FAQ ================================

Mon, 04 Aug 1997 14:32:23 GMT

Paul Rhod
#3 / 4

ctl3dv2.dll * MS-Office = CRASH!!!

Quote:

>Beware of leaving the DLL registered. I was getting all of these GPF's
>during design mode, until I changed my method of implementing 3d
>dialogs.
>What I do now (and haven't gotten a single GPF w/ lot's of other
>programs running) is to register the DLL, the Call the Dialog, the
>unregister the dialog. Something like...

Better to only register the DLL if you are not in design mode. Here's the
relevant bit of my register function:

Dim WinDir as String * 150
[...]
Inst% = GetWindowWord(MasterForm.hWnd, GWW_Hinstance)
'CTL3DV2 seems to accept an instance handle instead
'of a module handle, but can't be too careful, so...
Inst% = GetInstanceModule(Inst%)
res% = GetModuleFileName(Inst%, Windir, Len(Windir))
If InStr(Left(Windir, res%), "VB.EXE") Then
Beep
Inst% = -1
Else
res% = Ctl3dRegister(Inst%)
res% = Ctl3dAutoSubClass(Inst%)
End If

The other thing to watch out for is untrapped runtime errors: if your program
crashes out whilst ctl3d is registered, Windows will become unstable.

"The trouble with the drink talking is that the drink knows too much"

Tue, 05 Aug 1997 01:05:29 GMT

Peter G. Milla
#4 / 4

ctl3dv2.dll * MS-Office = CRASH!!!

Quote:

>>Beware of leaving the DLL registered. I was getting all of these GPF's
>>during design mode, until I changed my method of implementing 3d
>>dialogs.

[some stuff of mine, and Paul's munched]

Quote:

>The other thing to watch out for is untrapped runtime errors: if your program
>crashes out whilst ctl3d is registered, Windows will become unstable.

You can say that again :) Since I've changed my method, Windows has
only bombed once in design mode even while not implemeting the code
you showed earlier. (Luckily I use OS/2 so this is no big deal
<g>...see other WARP thread).

As to the slow down in the app...I have not noticed any slowdown even
on a slower 486 SX25 machine.

--
----------------------------------------------------------------------------
Peter G. Millard //////////////// "Error reading Drive A:

Co-Maintainer of comp.lang.basic.visual FAQ ================================

Mon, 11 Aug 1997 06:11:40 GMT