1 Replies - 778 Views - Last Post: 29 October 2018 - 02:29 PM Rate Topic: -----

#1 rdprecure   User is offline

  • New D.I.C Head

Reputation: 0
  • View blog
  • Posts: 1
  • Joined: 30-September 18

Issue with DLL component

Posted 30 September 2018 - 12:49 PM


Can someone explain what is happening with this situation?

I have an app that was written in VB6 which uses msxml6.dll to provide XML functionality.to XML documents. It works fine on System A, but not on System B.

When I try to run the app on System B in the VB6 IDE I get the following error...

Posted Image

...referring to this line of code...

Private Sub ProcessXMLOutput(flexgrid As MSFlexGrid, passedxdoc As MSXML2.DOMDocument30, passedxnode As MSXML2.IXMLDOMNode)

After several hours of troubleshooting I'm wondering if it has something to do with the System32 vs SysWOW64.

On System A (the one that works) the registry shows only one win32 entry for msxml6.dll:

Posted Image

On System B (the one that doesn't work) the registry shows two entries, one for win32 and one for win64:

Posted Image

Can someone explain what's going on with this and a possible fix?

Thank you...Doug

Attached image(s)

  • Attached Image
  • Attached Image
  • Attached Image

Is This A Good Question/Topic? 0
  • +

Replies To: Issue with DLL component

#2 raziel_   User is offline

  • Like a lollipop
  • member icon

Reputation: 469
  • View blog
  • Posts: 4,281
  • Joined: 25-March 09

Re: Issue with DLL component

Posted 29 October 2018 - 02:29 PM

User-defined type not defined means that for some reason the code could not find the DLL in the System B. What you can do is if you have access to System B is to try and reference it in VBA or VB6. On other hand not only msxml6.dll is used in that code that you have shown. Maybe the flex grid DLL is missing have you checked that?
Was This Post Helpful? 0
  • +
  • -

Page 1 of 1