CodeGuru Home VC++ / MFC / C++ .NET / C# Visual Basic VB Forums Developer.com
Results 1 to 3 of 3
  1. #1
    Join Date
    Jul 2003
    Location
    I'm Here!
    Posts
    31

    Failed to load commondialog....

    Hi,

    I have a user that has converted from WINNT to WINDOWS XP and they are getting the following error:

    Run-Time error 372:

    Failed to load control CommonDialog from 'comdlg32.ocx'. Version may be out of date, blah, blah, blah.....

    Both versions of the OCX match. Could this possibly have something to do with write access given to the individual user?

    My DLL is version 5.something and theirs is 6.something, but both versions of the OCX are the same. Should this matter since the DLL is supposed to be backwards compatible?

    TIA for any help.

  2. #2
    Join Date
    Oct 2003
    Location
    .NET2.0 / VS2005 Developer
    Posts
    7,104
    it isnt exactly a dll..
    ocx are registered in teh registry; bundling an ocx with your app may not be enough

    how can the versions be the same when you say you have v5 and they have v6?
    "it's a fax from your dog, Mr Dansworth. It looks like your cat" - Gary Larson...DW1: Data Walkthroughs 1.1...DW2: Data Walkthroughs 2.0...DDS: The DataSet Designer Surface...ANO: ADO.NET2 Orientation...DAN: Deeper ADO.NET...DNU...PQ

  3. #3
    Join Date
    Jul 2003
    Location
    I'm Here!
    Posts
    31
    The problem seems to be with user being logged on as Limited/Restricted user.

    When the app is installed with admin rights, the app registers and runs correctly.

    When the user switches to Limited/Restricted user, it gives the failed to load error.

    When the app is installed as Limited/Restricted user, it will fail to self-register certain DLLs including commoncontrol and commondialog.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  





Click Here to Expand Forum to Full Width

Featured