Hi Debbie:
I would run Dependency Walker (http://www.dependencywalker.com/) on the
connectcom.dll and make sure all the files needed for this DLL are on the
machine and are the proper versions.
I hope this helps.
This posting is provided "AS IS" with no warranties, and confers no rights.
Sincerely,
Microsoft FoxPro Technical Support
Lee Mitchell
*-- VFP9 Public Beta Now Available!! --*
Download the VFP9 beta here: http://msdn.microsoft.com/vfoxpro/
*-- VFP8 HAS ARRIVED!! --*
Read about all the new features of VFP8 here:
http://www.universalthread.com/VisualFoxPro/News/VFP8Release.asp
Purchase VFP8 here:
http://shop.microsoft.com/Referral/Productinfo.asp?siteID=11518
Keep an eye on the product lifecycle for Visual FoxPro here:
http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
- VFP5 Mainstream Support retired June 30th, 2003
- VFP6 Mainstream Support retired Sept. 30th, 2003
>Hi Everyone
>I'm having trouble registering a file using the following:
>regsvr32 c:\connect\connectcom.dll
>The command works fine on my development machine, and on all client machines
>except one. In that instance I get the following error message:
>"LoadLibrary("c:\connect\connectcom.dll") failed - The specified module
>could not be found."
>All relevant VFP runtime files (VFP 7.0) are installed on the machine in
>question, so I'm really not sure what the problem is. I have checked for
>typos in the command, but there are none.
>Does anyone have any idea what could be causing this error?
>Many thanks!
Debbie - 09 Jun 2004 12:28 GMT
Thanks for the advise - I will download the utility today and see what it
comes up with.
Thanks!
> Hi Debbie:
>
[quoted text clipped - 44 lines]
>
> >Many thanks!
Debbie,
Are the two machines using the same OS? Are you sure you have security rights in that directory? Registering DLLs can sometimes require at least local Admin level rights.
Rick
> Hi Everyone
>
[quoted text clipped - 15 lines]
>
> Many thanks!
Debbie - 09 Jun 2004 12:33 GMT
Hi Rick
Yes, they are both running the same OS - Windows 2000. I didn't think about
security rights issues, my first thought was that there was something wrong
with the DLL file as my experience building COMs is so limited. Given the
client I was connected to, I'll bet that's what it was! I'll check later
this morning and let you know.
Thanks - Debbie
Debbie,
Are the two machines using the same OS? Are you sure you have security
rights in that directory? Registering DLLs can sometimes require at least
local Admin level rights.
Rick
> Hi Everyone
>
[quoted text clipped - 15 lines]
>
> Many thanks!