• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2849
  • Last Modified:

Error in Loading DLL in Visual Basic program w/ MS Word macros

Hi!
I'm usually good at figuring these things out, but I am stuck. I just got a new laptop that has XP Pro and everything is a little different. I ran a program that worked fine on my old desktop computer, but seems to be missing a DLL now.

It's a VB6 program that takes data from a database and formats it to paste into Word (I have Office 2000). The error is on the line where I first use my word document, after I initialize the word.application. Here's a segment of the code:

'open up a new word document
    Dim Projects As New Word.Application
    With Projects
        .WindowState = wdWindowStateNormal
        .Documents.Add "Normal.dot", , , True
        .Visible = True
...

When I run I get an error that says Run-time error 48: Error in loading DLL. On debug, it highlights the "With Projects" line.

So I'm assuming it has to do with old references not working in XP, but I don't know how to find out which DLL is causing the problem or what I need to do to fix it.

Thanks!!
Paix120
0
paix120
Asked:
paix120
  • 9
  • 2
  • 2
  • +1
1 Solution
 
paix120Author Commented:
p.s. I added Set Projects = New Word.Application and still get the same error, except now it's on this line. Seems to come up as soon as I try to use the word.application I created.
0
 
Tommy KinardCommented:
Hi paix120,
Try it this way

Set Projects = CreateObject("Word.Application")

HTH
dragontooth

0
 
paix120Author Commented:
nope. same error.
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
tedunniCommented:
You might have tried this, but I recently had a similar problem.  What I did was to go to Start/Programs/Microsoft Visual Studio 6/Microsoft Visual Studio 6 Tools/Depends.

Using this program "Dependency Walker", you can select a dll and it will go out and tell you what other dll's it needs.  It highlighted a couple of dll's that I needed and when I copied them into the directory that I was working on, my problem was fixed.

Good luck.

0
 
Tommy KinardCommented:
Ok is Word installed on the laptop?

dragontooth

0
 
paix120Author Commented:
Yes word is installed.

tedunni - sounds like a great idea, i've never heard of that. how do you use it? i'm not sure what dlls are in my project, so how do i know which ones to open? is there a way to tell which dlls are added when you add a reference in VB? (the DLLs are not explicitly in the code...)

thanks!
paix120
0
 
tedunniCommented:
To be honest, I'm not too sure how to tell which dll's are added when you add a reference in VB, beside the actuall dll that is being added.  In the problem that I had, it was pretty obvious what dll was giving me problems.  So when I loaded this into dependency walker, it went out and found other dll's that were needed.
0
 
paix120Author Commented:
hmmm... I can't figure out which dll is causing the problem.
Anyone know which dll is involved with ADO connection or with Word.Application? And how do I find out what the problem is when the error is so vague?
0
 
paix120Author Commented:
just as a test, i tried excel.application and got the same exact error... does it have something to do with MSO9.dll - the microsoft object library?
0
 
paix120Author Commented:
when i run dependencies on the .exe, MSO9 doesn't come up...
0
 
paix120Author Commented:
ok, i tried running:
regsvr32 "c:\program files\microsoft office\office\mso9.dll"

and got the error:
"C:\.....\mso9.dll was loaded, but the DLLRegisterServer entry point was not found. This file can not be registered."

What does that mean??
0
 
paix120Author Commented:
OK my friend solved the problem. It seems to only be a problem with XP Pro, not Win 2000.

You have to do late binding instead of early binding, i.e. dim it as "object" instead of "excel.application". However, I still had to reference the excel9.olb as well.

Hopefully that will help anyone that comes across this post. Nothing else I found online seemed to work!

Thanks for your help,
Renee
0
 
paix120Author Commented:
My friend says that the late binding does have its disadvantages - it may take up more memory, and also since it doesn't know what object you're talking about, it doesn't help you as much during development. But at least it solved the dll error I was getting!
0
 
skahlNNICommented:
I had a similar problem with Outlook 2000 in Windows 2000, and calling the variable an object rather than outlook.application worked.

Thanks for posting your solution - it looks like it'd work for any of the Office 2000 programs and not just Excel.
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

  • 9
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now