VB6 ShellLnk Library

[gavjb]

Hi,

I am using the ShellLnk.dll Library (comes on VB6 Pro & Enterprise Cd's), but when trying to run the app on the client PC's I get Cannot find file error all the time, through debugging I have isolated it to the ShellLnk library.

I have created a install package with the Package and Deployment Wizard.

Has Anyone had any expereince with this library and how to get it working on client PC's?

 

[macleod1021]

First thing to do is do a search on the users hard drive and see if it's there. If it is, then their PATH statement in the Environment Variables may not include that location. Either move the dll to a path location or include the dll's path in the Environment Path.

If it's not on their hard drive at all, then the P&D may not have included it in the package. It's been a while since I've went through the wizard, but there's a screen that lets you choose additional files and where to copy them to. Make sure that the dll has a checkmark next to it(or add it) and put it in either the c:\%system dir% or the app's directory so your executable can find it.

That should fix it.

 

[gavjb]

I have just done a check and the file is copied onto the machine as part of the install, I have also tried regvr32 c:\winnt\system32\shelllnk.dll. But neither seems to solve the problem, this seems strange as previously, I have found that adding the library to the install copies and registers the file correctly.

 

[macleod1021]

Yes, the install package will register the file automatically. What operating system are you developing on and installing to? I found that if you attempt to install a package on an OS other than what it was developed on you can have spotty wierd issues like this. I was consistently able to reproduce the issue when trying to develop on Win 2000/XP and installing to Win9x(or vice-versa). The problem is that you're running into the infamous dll hell. I've spent a lot of time trying to remedy this in the past and actually gave up. I now have a laptop that runs win9x to develop on in case I need to do so. Not the "best" way, but I got tired of buying cases of aspirin every time I ran into this issue.

 

[gavjb]

the Setup is Windows 2000 Pro (for both development and users) with VB6 SP6 and Office 2000.