Deploy VB application

3 Sep 2010 11:35 AM

Harsha

Hi All,

I have created VB 6 application. Application has
- .exe files
- .dll files
- Server dll Files.

COM is setup in server with server dll files. For client .exe files
and middle layer .dll files has to be copied and there should be
connection between client and server.

I have exported proxy from server and installed it in client PC.

I have created setup and deployment project using VB tool. Files are
copied as expected. But client is unable to create object of COM
server class.
That is failing when I execute line CreateObject("DLLName.Classname").

That means connection between server and client not happening.

Am I missig something here? PLease can anybody advice on this.

Your help is appreciated in advance
Thanks
Harsha

3 Sep 2010 2:51 PM

ralph

On Fri, 3 Sep 2010 04:35:59 -0700 (PDT), Harsha
<sriharsha.ga***@gmail.com> wrote:

Show quoteHide quote

>Hi All,
>
>I have created VB 6 application. Application has
>- .exe files
>- .dll files
>- Server dll Files.
>
>COM is setup in server with server dll files. For client .exe files
>and middle layer .dll files has to be copied and there should be
>connection between client and server.
>
>I have exported proxy from server and installed it in client PC.
>
>I have created setup and deployment project using VB tool. Files are
>copied as expected. But client is unable to create object of COM
>server class.
>That is failing when I execute line CreateObject("DLLName.Classname").
>
>That means connection between server and client not happening.
>

Would be helpful to know the exact error you are getting. There can be
many causes for failure.

example:
    ' this uses the symbol that came from for a type library
            ' you set in Project References
    ' ie, it resolves the "VB Project Reference" to a specific
    ' CLSID (GUID)
      Dim obj As <VB Project Reference>.Classname
    ' this is using an AppID/ProgID
    ' The COM server will look-up the CLSID in the Registry to
    ' and then use that CLSID to resolve to a specific component
      Set obj = CreateObject("DLLName.Classname")

If you have an error it could because ...
1) The Registry doesn't have an entry for "DLLName.Classname".
2) The Registery entry doesn't match the Project Reference
3) The Registery entry resolves to a component that doesn't exist, is
located some place the Program doesn't have permission to peek, etc.
4) The Interface Declaration used to compile doesn't match the
Interface a component can supply
5) ... any thing else that can go wrong. <g>

-ralph