| Title: | Microsoft Visual Basic |
| Moderator: | TAMARA::DFEDOR::fedor |
| Created: | Thu May 02 1991 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2565 |
| Total number of notes: | 10453 |
We have a VB application that, when running under NT and trying to display the "Save As" Common Dialog box, gives the following error message: The common dialog function failed during initialization. This error often occurs when insufficient memory is available. But the NT PC had 64Meg of memory, and the common dialog box simply doesn't take much memory. The problem isn't with the source code, since an "old" EXE runs fine, but making a new EXE with the old source code causes failure - but only on NT systems. Runs fine on Windows 95. The problem "may" be related to the fact that I installed VB5, and then continued to develop this application under VB4. I didn't suspect any problem since this problem didn't occur on my Windows 95 system. Its only when we installed this application on an NT system that the Browse function failed (the Browse button brings up the file common dialog box, which returns with that error). So I'm suspecting some sort of compatability problem, but I have no idea what. My last resort is to de-install VB5 and VB4, then re-install only VB4. But that seems like a brute-force solution, and I still won't know what the real problem was. Anyone run into this? Don
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2562.1 | EVTSG8::TOWERS | Fri May 30 1997 09:41 | 22 | ||
It sounds to me as if you have some incompatibility between DLLs on the
target machines and in particular that comdlg32.dll/ocx are involved.
In your place I would read up (I believe there may be something on
Microsoft site) about matching sets of DLLs/OCXs that have to be
delivered together to get a matching set which works. You have VB5 on
your machine but are building the kit, presumably, with the VB4 wizard.
It may not be doing everything required to make sure you deliver a
compatible set of DLLs etc.
Actually, thinking about it, in your place I would just migrate the app
to VB5 and have done with it. Deinstalling VB5, VB4 and reinstalling
VB4 is unlikely to fix the problem. You will probably have to go in and
physically delete some files before the reinstall. Of course to do that
you'll have to know which ones.
Note also that one of the DLLs you deliver will be a different file
depending on whether the target machine is 95 or NT. I forget which
one, Comctl32?
Cheers,
Brian
| |||||
| 2562.2 | EVTSG8::TOWERS | Fri May 30 1997 09:44 | 7 | ||
I forget to add, don't automatically blame VB5. Your problem may also
be related to applying a Service Pack, either 2 or 3. In any case the
bottom line is to make sure you deliver a consistent set of system
DLLs.
Cheers,
Brian
| |||||
| 2562.3 | suggestion | XSTACY::PATTISON | A rolling stone gets the worm | Tue Jun 03 1997 11:34 | 7 |
See also: http://www.microsoft.com/kb/articles/q167/1/21.htm Dave | |||||