Home All Groups Group Topic Archive Search About
Author
8 Aug 2010 11:22 PM
Mike Simpson
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

Author
8 Aug 2010 11:53 PM
Nobody
"Mike Simpson" <ag***@optusnet.com.au> wrote in message
news:e0cuCC1NLHA.1960@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/
Author
10 Aug 2010 3:12 AM
Mike Simpson
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@speranza.aioe.org...

"Mike Simpson" <ag***@optusnet.com.au> wrote in message
news:e0cuCC1NLHA.1960@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/
Author
10 Aug 2010 6:28 AM
GS
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
Author
10 Aug 2010 7:54 PM
James
On Aug 8, 7:22 pm, "Mike Simpson" <ag***@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.



Show quoteHide quote
>
> 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
Author
30 Aug 2010 9:25 PM
Simon Harder
Show quote Hide quote
"Mike Simpson" 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.
>
> 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
>
> .
>
Author
31 Aug 2010 2:47 AM
T Jones
Use the API to create the Common Dialog. That way, it will reply upon
Windows' own DLL's and not an OCX.


Show quoteHide quote
"Simon Harder" <Simon Har***@discussions.microsoft.com> wrote in message
news:A24E7717-43DF-4970-A741-F09E214C67AC@microsoft.com...
>
>
> "Mike Simpson" 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.
>>
>> 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
>>
>> .
>>
Author
30 Aug 2010 9:33 PM
Simon Harder
Hello Mike,

have you found a solution yet? I have encountered the same issue with a Vb6
app that installed fine on several Win7 machines a month ago.

Additionally I am running into all sorts of issues with the installed about
requiring admin permission to run even when logged in as admin  (telling me
my application wants to change the computer system ???) I am guessing that I
am running into multiple issues but the unravelling with my limited
understanding of Win7 is proving difficult ( plus a slow connection for
GoToMeeting)

Any papers that could help me out?

R
Simon

Show quoteHide quote
"Mike Simpson" 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.
>
> 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
>
> .
>
Author
30 Aug 2010 10:55 PM
GS
Simon Harder brought next idea :
Show quoteHide quote
> Hello Mike,
>
> have you found a solution yet? I have encountered the same issue with a Vb6
> app that installed fine on several Win7 machines a month ago.
>
> Additionally I am running into all sorts of issues with the installed about
> requiring admin permission to run even when logged in as admin  (telling me
> my application wants to change the computer system ???) I am guessing that I
> am running into multiple issues but the unravelling with my limited
> understanding of Win7 is proving difficult ( plus a slow connection for
> GoToMeeting)
>
> Any papers that could help me out?
>
> R
> Simon
>
> "Mike Simpson" 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.
>>
>> 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
>>
>> .
>>

Nobody's suggestion is still working for me on Win7x64 with VB6.exe
apps. Try it out and see if it serves you to not use the comdlg.ocx.

--
Garry

Free usenet access at http://www.eternal-september.org
ClassicVB Users Regroup! comp.lang.basic.visual.misc
Author
31 Aug 2010 4:12 AM
Abhishek
Open object browser and see.

Const cdlInitialization = 32765 (&H7FFD)
    Member of MSComDlg.ErrorConstants
    The function failed during initialization.




Show quoteHide quote
"Mike Simpson" <ag***@optusnet.com.au> wrote in message
news:e0cuCC1NLHA.1960@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'