Prev: finding position of worksheet
Next: Class Access
From: Mike Simpson on 8 Aug 2010 19:22
I have several VB6 programs which I have written using the Common Dialog box
COMDLG32.OCX and they all work fine.

Suddenly this week on my own PC (Windows 7 - 64 bit - Home Premium) all
these programs throw up the error
quote
Run-time error '32765'

The common dialog function failed during initialization. this error
often occurs when insufficient memory is available.
unquote
This error appears in both compiled versions of the programs and when using
the VB6 editor.

Placing an earlier copy of comdlg32.ocx in the same folder as the VB .exe
file and registering it worked for a while, but today
it has reverted back to the error messages.

Has anyone any idea why this is happening? I have 6 gigs of RAM installed so
memory is not the problem. All my programs
work fine on my XP SP3 machine and on many other users world-wide under
Windows 7. I am stumped as to why this is
happening here.

Regards, Mike Simpson
Penrith, NSW, Australia

From: Nobody on 8 Aug 2010 19:53
"Mike Simpson" <agene(a)optusnet.com.au> wrote in message
news:e0cuCC1NLHA.1960(a)TK2MSFTNGP05.phx.gbl...
>I have several VB6 programs which I have written using the Common Dialog
>box COMDLG32.OCX and they all work fine.
>
> Suddenly this week on my own PC (Windows 7 - 64 bit - Home Premium) all
> these programs throw up the error
> quote
> Run-time error '32765'

Toss it out and use the Windows API directly, so there is no need to include
the extra OCX. Here are some samples(Scroll down to "File Dialogs"):

http://vbnet.mvps.org/code/comdlg/


From: Mike Simpson on 9 Aug 2010 23:12
Thanks for that, but I had already tried that using code from another site.
Although most of the dialog boxes appeared, the Open and Save ones still did
not open.

I have now reverted my system to 1st August and all is working correctly
once more.

Either a Microsoft Fix or something else I had installed this month must
have broken the cmdlg box.

Regards, Mike Simpson
Penrith, NSW, Australia


"Nobody" wrote in message news:i3ng2p$mq2$1(a)speranza.aioe.org...

"Mike Simpson" <agene(a)optusnet.com.au> wrote in message
news:e0cuCC1NLHA.1960(a)TK2MSFTNGP05.phx.gbl...
>I have several VB6 programs which I have written using the Common Dialog
>box COMDLG32.OCX and they all work fine.
>
> Suddenly this week on my own PC (Windows 7 - 64 bit - Home Premium) all
> these programs throw up the error
> quote
> Run-time error '32765'

Toss it out and use the Windows API directly, so there is no need to include
the extra OCX. Here are some samples(Scroll down to "File Dialogs"):

http://vbnet.mvps.org/code/comdlg/

From: GS on 10 Aug 2010 02:28
Actually, Nobody's suggestion works very well (for me, at least).

You are aware that Win7 does not ship with comdlg32.ocx, aren't you?
This control must be distributed with you app and properly registered
on the target machine in order to use it with Win7.

for a list of other runtimes not shipped with Win7, see this:
http://msdn.microsoft.com/en-us/vbasic/ms788708.aspx

--
Garry

Free usenet access at http://www.eternal-september.org
ClassicVB Users Regroup! comp.lang.basic.visual.misc


From: James on 10 Aug 2010 15:54
On Aug 8, 7:22 pm, "Mike Simpson" <ag...(a)optusnet.com.au> wrote:
> I have several VB6 programs which I have written using the Common Dialog box
> COMDLG32.OCX and they all work fine.
>
> Suddenly this week on my own PC (Windows 7 - 64 bit - Home Premium) all
> these programs throw up the error
> quote
> Run-time error '32765'
>
> The common dialog function failed during initialization. this error
> often occurs when insufficient memory is available.
> unquote
> This error appears in both compiled versions of the programs and when using
> the VB6 editor.
I had this problem years ago, where this would crop up on some
machines but not on others.

In my case, the culprit turned out to be in the flags. I had set a
flag that, if I remember correctly,
had something to do with "read only" directories. Changing my code so
that this
flag didn't get set cleared up the problem.



>
> Placing an earlier copy of comdlg32.ocx in the same folder as the VB .exe
> file and registering it worked for a while, but today
> it has reverted back to the error messages.
>
> Has anyone any idea why this is happening? I have 6 gigs of RAM installed so
> memory is not the problem. All my programs
> work fine on my XP SP3 machine and on many other users world-wide under
> Windows 7. I am stumped as to why this is
> happening here.
>
> Regards, Mike Simpson
> Penrith, NSW, Australia

 | 
Pages: 1
Prev: finding position of worksheet
Next: Class Access