Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Referencing a DLL

Status
Not open for further replies.

Alleyopp

Programmer
Sep 17, 2004
22
US
I need a little help here.

I am attempting to connect VB 6 to LiveLink. To do so there are some LiveLink DLLs that VB needs to use.

The instructions to do this are simply:
"The application's working directory must include all referenced LAPI *.dll files."

Ok, can someone please tell me what that means..
I have tried to put the DLLs in my code directory but it complains it cant find them (file not found).
I attempted to user regsvr32 on it but it gave me an error :
...DLL was loaded but the DLLRegisterServer entry Point ws not found (WHAT DOES THAT MEAN???)
...DLL may not be exported or a corrupt version of ...DLL may be in memory. Consider using PView to detect and remove it.

OK, first of all can someone point me to some good doc that explains the .DLL thing. What is it, how it works, how to register them so on..

And also any help in the above error would be great.

Thanks
Alley
 
How are you running the program - via the IDE or exe file?

If it's the exe, then put the dll files in the same directory where the exe file is located. You will probably have to set up a shortcut to the exe to define the startup directory as the directory that the program runs from.

If you're running from the IDE, you will need to put the dll files in the directory that VB is set to start up in. Look at the shortcut you use to run VB with. In mine (on the start bar), its "C:\Program Files\Microsoft Visual Studio\VB98". You can change the startup directory for VB also in the shortcut. I do that so I can have the default save directory point to my project area and not VB's area.

On the dll registration snafu you ran into - there are 2 kinds of dll files - those that require registration (and these are activeX/com objects) and those that are just libraries of routines, but cannot be registered. It appears the ones you are using are in the library category.

"I think we're all Bozos on this bus!" - Firesign Theatre [jester]
 
Thanks ArtieChoke..
That worked... Putting it in the VB directory did the trick.
I was under the impression I need to put it where I was putting my project code...

Thanks Much
Alley
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top