Re: Registering DLL issue.

Thanks for the information. But for some reason, today it seems to be
working fine, with it pointed to the system32 folder, can't explain it
but it's working.

On Sep 12, 2:38 pm, "Ken Halter"
<Ken_Halter@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
<sami...@xxxxxxxxx> wrote in message

news:1189620468.407347.279420@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

I keep a dll on a network drive. when user needs it I will go to
their computer and copy it from network drive and put it in their
system32 drive and use regsvr32 to register it. But it doesn't seem
to work correctly, because when I open up the program the references
are pointing to the dll on the network drive and not the dll i
registered in the system32 folder.

When I made the programmed it is pointing to my system32 folder and
not the network drive. what could be going on and how do i fix?

samir

Does the app work when it's registered on the network drive? If you've
re-built the DLL recently without maintaining binary compatibility, your
project probably still points to the old copy. RegClean should fix that.

FYI, there's no requirement that ActiveX dlls be placed in Sys32. They can
be anywhere at all, as long as they're properly registered and available.
Personally, I keep everything I build out of Sys32. It's cluttered already
with unrecognizable stuff <g>

All of my source is on our server so it's backed up every night. When I
build, the resulting binary ends up on the server (unless I tell it
otherwise, which is rare) and, if it's an ActiveX component, it's registered
on the server, too (VB does it during compile)... I start asking questions
when my dlls /aren't/ registered on the server.

...but, "their system32 drive"... does that mean VB's IDE is installed on
every workstation you copy this DLL to?

--
Ken Halter - MS-MVP-VB - Please keep all discussions in the groups..
In Loving Memory -http://www.vbsight.com/Remembrance.htm


.

Relevant Pages

  • Re: VB6 Regfree Com
    ... The dll itself is a standard dll and needs no registering. ... It allows you to instantiate objects from COM servers *without* the need to register them. ... The COM server file may be anywhere on disk, not necessarily in the application directory. ... The only difference is that for instantiating you must not use VBs New operator or VBs CreateObject method. ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6 Regfree Com
    ... MSVBVM60.DLL is on the target machine, then I can just include this DLL, the ... The COM server file may be anywhere on disk, ... Register the COM server you want to use *on the development pc*. ...
    (microsoft.public.vb.general.discussion)
  • Re: runtime error 800a0030 when executing vbscript from w2k. Works
    ... The COM server (it is not DLL, but out proc exe) is registered on both ... I forgot to mention more about the enviroment, but basically the COM Server ... > Does the dll register correctly as a COM component? ...
    (microsoft.public.scripting.vbscript)
  • Re: Updating CDO.DLL on BlackBerry Server
    ... > After applying the 828429 hotfix to our Exchange server, ... > BES must match or exceed that of the CDO.DLL on the ... must the DLL file be in the correct location ... because the location that you register it from is also saved as part of the ...
    (microsoft.public.exchange.admin)
  • Re: Help in WMI in ASP.net application
    ... In my option you did the correct thing by creating a COM+ DLL. ... step I see you missing is that you need to register the DLL in COM+. ... The parameters that we pass or the server name (the host ... > well as from a remote machine it is giving the correct result. ...
    (microsoft.public.scripting.wsh)
Loading