Calling a DLL

[Big John]

I have created a DLL and a calling program. The problem that I'm having is
that the DLL is stored on the a server as well the executable. When ever
the program is executed it is on the same server as the DLL. Both programs
vary locations becuase they are run at different sites. So my question is
how do I tell the calling program where the DLL is located? Since the executable
is run off multiple users PCs how do you register this infomration on the
users machine of where to look for the DLL?


Thanks for the help!
Big John

[Jack J]

Why not put it in the com+, then you can generate/install the client side
package for the user's pcs, which will register the components in the users
pc, then scm will take care the rest...

"Big John" <programminginfo@yahoo.com> wrote:
>
>I have created a DLL and a calling program. The problem that I'm having
is
>that the DLL is stored on the a server as well the executable. When ever
>the program is executed it is on the same server as the DLL. Both programs
>vary locations becuase they are run at different sites. So my question
is
>how do I tell the calling program where the DLL is located? Since the executable
>is run off multiple users PCs how do you register this infomration on the
>users machine of where to look for the DLL?
>
>
>Thanks for the help!
>Big John

[Big John]

How do I go about doing that?
Can you explain how this is done or provide a site to see how to do this?

Thanks again!

"Jack J" <szrichy@163.net> wrote:
>
>
>Why not put it in the com+, then you can generate/install the client side
>package for the user's pcs, which will register the components in the users
>pc, then scm will take care the rest...
>
>"Big John" <programminginfo@yahoo.com> wrote:
>>
>>I have created a DLL and a calling program. The problem that I'm having
>is
>>that the DLL is stored on the a server as well the executable. When ever
>>the program is executed it is on the same server as the DLL. Both programs
>>vary locations becuase they are run at different sites. So my question
>is
>>how do I tell the calling program where the DLL is located? Since the
executable
>>is run off multiple users PCs how do you register this infomration on the
>>users machine of where to look for the DLL?
>>
>>
>>Thanks for the help!
>>Big John
>

[Jack J]

OK,
1- create a normal VB Dll project and compile,
2- at the com+ server, open component explore tool, use the gui to create
a new application, import the dll, and right clikc to export a client side
install package,
3- copy this package to client workstation and run it,
4- create a normal exe project and reference ths dll progid and do something
like the component is on the local machine.

JJ


"Big John" <programminginfo@yahoo.com> wrote:
>
>How do I go about doing that?
>Can you explain how this is done or provide a site to see how to do this?
>
>Thanks again!
>
>"Jack J" <szrichy@163.net> wrote:
>>
>>
>>Why not put it in the com+, then you can generate/install the client side
>>package for the user's pcs, which will register the components in the users
>>pc, then scm will take care the rest...
>>
>>"Big John" <programminginfo@yahoo.com> wrote:
>>>
>>>I have created a DLL and a calling program. The problem that I'm having
>>is
>>>that the DLL is stored on the a server as well the executable. When ever
>>>the program is executed it is on the same server as the DLL. Both programs
>>>vary locations becuase they are run at different sites. So my question
>>is
>>>how do I tell the calling program where the DLL is located? Since the
>executable
>>>is run off multiple users PCs how do you register this infomration on
the
>>>users machine of where to look for the DLL?
>>>
>>>
>>>Thanks for the help!
>>>Big John
>>
>