Re: Access runtime 2003 with Common Dialog DLL

comdlg32.dll seems to be one of the most sensitive to version differences.

What are you using that dll for? Can you replace it by making API calls
instead?

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)



"Stan Lukken" <StanLukken@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:874B6A35-1EF3-4B69-989C-433D39CF4568@xxxxxxxxxxxxxxxx
> I've built an MDE application, packaged and installed with tools from the
> Developer Extensions. The application installs without error and runs
> perfectly on several computers. Runtime warnings occur only on a few
> specific computers. The difference in configuration between those systems
> that do and those that do not generate warnings is not clear. All systems
> run the XP OS with all critical updates for both the OS and Office, if
> Office
> is installed. My MDE runs without warnings on machines that include
> Office
> XP Pro and on machines that do not have any version of Office on them.
> The
> two machines that generate warnings appear unique in that they include
> Office
> XP Standard (without Access).
>
> Because my MDE makes use of "comdlg32.dll", I suspect a registration
> problem. The initial form presented to the user includes a common dialog
> object. Before the form is displayed, a warning message says "There is no
> object in this control". The application's initial form will then
> display,
> but any attempt to use a control that refers to the common dialog object
> will
> generate additional warning messages saying the class or object does not
> support the set of events. My attempts to register the DLL using
> "regsvr32"
> results in the message "comdlg32.dll was loaded, but the DLLRegisterServer
> entry point was not found. This file cannot be registered."
>
> My questions? Is this a registration problem with "comdlg32.dll", and if
> so, how can I resolve it? If not, why does my MDE operate without flaw on
> other machines where no manual registration of the dll was ever performed?
> Thank for your help. . .


.

Relevant Pages

  • Re: Access runtime 2003 with Common Dialog DLL
    ... DLL have always worked well for me in the past, ... The application installs without error and runs ... >> that do and those that do not generate warnings is not clear. ... >> XP Pro and on machines that do not have any version of Office on them. ...
    (microsoft.public.access.setupconfig)
  • Access runtime 2003 with Common Dialog DLL
    ... The application installs without error and runs ... that do and those that do not generate warnings is not clear. ... My MDE runs without warnings on machines that include Office ... XP Pro and on machines that do not have any version of Office on them. ...
    (microsoft.public.access.setupconfig)
  • Re: Perl threads - capturing value returned from sub
    ... use strict; ... use warnings; ... my @machines = qw; ...
    (comp.lang.perl.misc)
  • Re: Perl threads - capturing value returned from sub
    ... use strict; ... use warnings; ... my @machines = qw; ...
    (comp.lang.perl.misc)
  • Re: Exporting stl class
    ... and it seems to work with valarray too. ... For the warnings, ... before template instantiation ... // Exported from DLL: ...
    (microsoft.public.vc.language)