passing parameters to another running VB application


DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 15 of 15

Thread: passing parameters to another running VB application

  1. #1
    Hian Chew Guest

    passing parameters to another running VB application


    Hi,
    I have 2 independent VB applications running.
    If I want to pass some parameters from prog A to prog B,
    so that prog B can process the parameters and update its
    display, what do I have to do in codes for these 2 programs
    in order to do that?

    Hian

  2. #2
    mrfelis Guest

    Re: passing parameters to another running VB application

    Two choices:

    If you like subclassing, check into Karl's PrevInst.zip sample:

    http://www.mvps.org/vb/samples.htm

    Otherwise, make 1 or both applictions Active X. This way you can make the
    programs communicate directly through COM.


    App1:
    clsPublicInterface

    Public Sub DoSomething()
    ....
    End sub


    App2: (Add reference to App1)
    set oApp1 = GetObject(,"App1.clsPublicInterface")
    if not oApp1 is Nothing then
    oApp1.DoSomething
    else
    msgbox "app1 not running"
    end if

    --
    ~~~
    !ti timda I ,KO
    ..em deppals nocaeB sivaM
    !draH
    ~~
    C'Ya,
    mrfelis@yahoo!com
    Hian Chew <hschew00@yahoo.com> wrote in message
    news:3b55fec4$1@news.devx.com...
    >
    > Hi,
    > I have 2 independent VB applications running.
    > If I want to pass some parameters from prog A to prog B,
    > so that prog B can process the parameters and update its
    > display, what do I have to do in codes for these 2 programs
    > in order to do that?
    >
    > Hian




  3. #3
    mrfelis Guest

    Re: passing parameters to another running VB application

    Two choices:

    If you like subclassing, check into Karl's PrevInst.zip sample:

    http://www.mvps.org/vb/samples.htm

    Otherwise, make 1 or both applictions Active X. This way you can make the
    programs communicate directly through COM.


    App1:
    clsPublicInterface

    Public Sub DoSomething()
    ....
    End sub


    App2: (Add reference to App1)
    set oApp1 = GetObject(,"App1.clsPublicInterface")
    if not oApp1 is Nothing then
    oApp1.DoSomething
    else
    msgbox "app1 not running"
    end if

    --
    ~~~
    !ti timda I ,KO
    ..em deppals nocaeB sivaM
    !draH
    ~~
    C'Ya,
    mrfelis@yahoo!com
    Hian Chew <hschew00@yahoo.com> wrote in message
    news:3b55fec4$1@news.devx.com...
    >
    > Hi,
    > I have 2 independent VB applications running.
    > If I want to pass some parameters from prog A to prog B,
    > so that prog B can process the parameters and update its
    > display, what do I have to do in codes for these 2 programs
    > in order to do that?
    >
    > Hian




  4. #4
    Alex Guest

    Re: passing parameters to another running VB application


    One more choice

    MSDN article
    Q176058 - HOWTO: Pass String Data Between Applications Using SendMessage


    http://support.microsoft.com/support.../Q176/0/58.ASP

    Alex


    "mrfelis" <mrfelis@yahoo.NOSPAM.com> wrote:
    >Two choices:
    >
    >If you like subclassing, check into Karl's PrevInst.zip sample:
    >
    >http://www.mvps.org/vb/samples.htm
    >
    >Otherwise, make 1 or both applictions Active X. This way you can make the
    >programs communicate directly through COM.
    >
    >
    >App1:
    >clsPublicInterface
    >
    >Public Sub DoSomething()
    >....
    >End sub
    >
    >
    >App2: (Add reference to App1)
    >set oApp1 = GetObject(,"App1.clsPublicInterface")
    >if not oApp1 is Nothing then
    > oApp1.DoSomething
    >else
    > msgbox "app1 not running"
    >end if
    >
    >--
    >~~~
    > !ti timda I ,KO
    >..em deppals nocaeB sivaM
    >!draH
    >~~
    >C'Ya,
    >mrfelis@yahoo!com
    >Hian Chew <hschew00@yahoo.com> wrote in message
    >news:3b55fec4$1@news.devx.com...
    >>
    >> Hi,
    >> I have 2 independent VB applications running.
    >> If I want to pass some parameters from prog A to prog B,
    >> so that prog B can process the parameters and update its
    >> display, what do I have to do in codes for these 2 programs
    >> in order to do that?
    >>
    >> Hian

    >
    >



  5. #5
    Alex Guest

    Re: passing parameters to another running VB application


    One more choice

    MSDN article
    Q176058 - HOWTO: Pass String Data Between Applications Using SendMessage


    http://support.microsoft.com/support.../Q176/0/58.ASP

    Alex


    "mrfelis" <mrfelis@yahoo.NOSPAM.com> wrote:
    >Two choices:
    >
    >If you like subclassing, check into Karl's PrevInst.zip sample:
    >
    >http://www.mvps.org/vb/samples.htm
    >
    >Otherwise, make 1 or both applictions Active X. This way you can make the
    >programs communicate directly through COM.
    >
    >
    >App1:
    >clsPublicInterface
    >
    >Public Sub DoSomething()
    >....
    >End sub
    >
    >
    >App2: (Add reference to App1)
    >set oApp1 = GetObject(,"App1.clsPublicInterface")
    >if not oApp1 is Nothing then
    > oApp1.DoSomething
    >else
    > msgbox "app1 not running"
    >end if
    >
    >--
    >~~~
    > !ti timda I ,KO
    >..em deppals nocaeB sivaM
    >!draH
    >~~
    >C'Ya,
    >mrfelis@yahoo!com
    >Hian Chew <hschew00@yahoo.com> wrote in message
    >news:3b55fec4$1@news.devx.com...
    >>
    >> Hi,
    >> I have 2 independent VB applications running.
    >> If I want to pass some parameters from prog A to prog B,
    >> so that prog B can process the parameters and update its
    >> display, what do I have to do in codes for these 2 programs
    >> in order to do that?
    >>
    >> Hian

    >
    >



  6. #6
    Hian Chew Guest

    Re: passing parameters to another running VB application


    Can you give a very simple example on how to create this:

    >App1:
    >clsPublicInterface
    >
    >Public Sub DoSomething()
    >....
    >End sub


    Thanks for the tips




    "mrfelis" <mrfelis@yahoo.NOSPAM.com> wrote:
    >Two choices:
    >
    >If you like subclassing, check into Karl's PrevInst.zip sample:
    >
    >http://www.mvps.org/vb/samples.htm
    >
    >Otherwise, make 1 or both applictions Active X. This way you can make the
    >programs communicate directly through COM.
    >
    >
    >App1:
    >clsPublicInterface
    >
    >Public Sub DoSomething()
    >....
    >End sub
    >
    >
    >App2: (Add reference to App1)
    >set oApp1 = GetObject(,"App1.clsPublicInterface")
    >if not oApp1 is Nothing then
    > oApp1.DoSomething
    >else
    > msgbox "app1 not running"
    >end if
    >
    >--
    >~~~
    > !ti timda I ,KO
    >..em deppals nocaeB sivaM
    >!draH
    >~~
    >C'Ya,
    >mrfelis@yahoo!com
    >Hian Chew <hschew00@yahoo.com> wrote in message
    >news:3b55fec4$1@news.devx.com...
    >>
    >> Hi,
    >> I have 2 independent VB applications running.
    >> If I want to pass some parameters from prog A to prog B,
    >> so that prog B can process the parameters and update its
    >> display, what do I have to do in codes for these 2 programs
    >> in order to do that?
    >>
    >> Hian

    >
    >



  7. #7
    Hian Chew Guest

    Re: passing parameters to another running VB application


    Can you give a very simple example on how to create this:

    >App1:
    >clsPublicInterface
    >
    >Public Sub DoSomething()
    >....
    >End sub


    Thanks for the tips




    "mrfelis" <mrfelis@yahoo.NOSPAM.com> wrote:
    >Two choices:
    >
    >If you like subclassing, check into Karl's PrevInst.zip sample:
    >
    >http://www.mvps.org/vb/samples.htm
    >
    >Otherwise, make 1 or both applictions Active X. This way you can make the
    >programs communicate directly through COM.
    >
    >
    >App1:
    >clsPublicInterface
    >
    >Public Sub DoSomething()
    >....
    >End sub
    >
    >
    >App2: (Add reference to App1)
    >set oApp1 = GetObject(,"App1.clsPublicInterface")
    >if not oApp1 is Nothing then
    > oApp1.DoSomething
    >else
    > msgbox "app1 not running"
    >end if
    >
    >--
    >~~~
    > !ti timda I ,KO
    >..em deppals nocaeB sivaM
    >!draH
    >~~
    >C'Ya,
    >mrfelis@yahoo!com
    >Hian Chew <hschew00@yahoo.com> wrote in message
    >news:3b55fec4$1@news.devx.com...
    >>
    >> Hi,
    >> I have 2 independent VB applications running.
    >> If I want to pass some parameters from prog A to prog B,
    >> so that prog B can process the parameters and update its
    >> display, what do I have to do in codes for these 2 programs
    >> in order to do that?
    >>
    >> Hian

    >
    >



  8. #8
    mrfelis Guest

    Re: passing parameters to another running VB application

    Alex <AlexanderBirman@Yahoo.com> wrote in message
    news:3b5716ff$1@news.devx.com...
    >
    > One more choice
    >
    > MSDN article
    > Q176058 - HOWTO: Pass String Data Between Applications Using SendMessage
    >
    >
    > http://support.microsoft.com/support.../Q176/0/58.ASP
    >
    > Alex
    >


    This is the same method Karl Peterson used. Karl wanted to talk to the
    previous instance of the same app. Little else is different from the
    samples.

    Now I didn't take a look at either sample's subclassing method. I prefer
    Matthew Curland's subclassing method.

    --
    ~~~
    !ti timda I ,KO
    ..em deppals nocaeB sivaM
    !draH
    ~~
    C'Ya,
    mrfelis@yahoo!com



  9. #9
    mrfelis Guest

    Re: passing parameters to another running VB application

    Alex <AlexanderBirman@Yahoo.com> wrote in message
    news:3b5716ff$1@news.devx.com...
    >
    > One more choice
    >
    > MSDN article
    > Q176058 - HOWTO: Pass String Data Between Applications Using SendMessage
    >
    >
    > http://support.microsoft.com/support.../Q176/0/58.ASP
    >
    > Alex
    >


    This is the same method Karl Peterson used. Karl wanted to talk to the
    previous instance of the same app. Little else is different from the
    samples.

    Now I didn't take a look at either sample's subclassing method. I prefer
    Matthew Curland's subclassing method.

    --
    ~~~
    !ti timda I ,KO
    ..em deppals nocaeB sivaM
    !draH
    ~~
    C'Ya,
    mrfelis@yahoo!com



  10. #10
    Ron Phillips Guest

    Re: passing parameters to another running VB application


    Create an ActiveX EXE project in VB. You'll get a class as the
    default object. Change the name of the class to "clsPublicInterface".
    Add some code to the class object:

    Option Explicit

    Public Function SetCaption(ByVal strArg As String)
    Form1.Caption = strArg
    End Function

    ----------

    Add a standard form to the project (Form1). Go to the project
    properties, and change the name of the project to "ActiveXTest".
    Change the Startup Object to "Sub Main". Click on the Component tab,
    and change the Start Mode to "Standalone". Add a module (Module1) to
    your project, and add some code:

    Option Explicit

    Sub main()
    Form1.Show
    End Sub

    ----------

    Now run the project. It should act like a regular EXE and show your
    Form1 window.

    ----------

    Now, open another instance of VB and create a Standard EXE project. Go
    to References and you'll see that "ActiveXTest" is listed there. Add
    a reference to that project. In the Load() event of your default
    form, add some code:

    Option Explicit

    Private Sub Form_Load()
    Dim c As New clsPublicInterface
    Call c.SetCaption("My caption")
    Set c = Nothing
    End Sub

    Now run the project, and what you'll find is that the caption of your
    ActiveX project form has just changed to "My caption", as you've
    passed it from one app to the ActiveX app.

    Hope this helps,
    Ron

    On 19 Jul 2001 21:13:03 -0700, "Hian Chew" <hschew00@yahoo.com> wrote:
    >
    >Can you give a very simple example on how to create this:
    >
    >>App1:
    >>clsPublicInterface
    >>
    >>Public Sub DoSomething()
    >>....
    >>End sub

    >
    >Thanks for the tips
    >
    >
    >
    >
    >"mrfelis" <mrfelis@yahoo.NOSPAM.com> wrote:
    >>Two choices:
    >>
    >>If you like subclassing, check into Karl's PrevInst.zip sample:
    >>
    >>http://www.mvps.org/vb/samples.htm
    >>
    >>Otherwise, make 1 or both applictions Active X. This way you can make the
    >>programs communicate directly through COM.
    >>
    >>
    >>App1:
    >>clsPublicInterface
    >>
    >>Public Sub DoSomething()
    >>....
    >>End sub
    >>
    >>
    >>App2: (Add reference to App1)
    >>set oApp1 = GetObject(,"App1.clsPublicInterface")
    >>if not oApp1 is Nothing then
    >> oApp1.DoSomething
    >>else
    >> msgbox "app1 not running"
    >>end if
    >>
    >>--
    >>~~~
    >> !ti timda I ,KO
    >>..em deppals nocaeB sivaM
    >>!draH
    >>~~
    >>C'Ya,
    >>mrfelis@yahoo!com
    >>Hian Chew <hschew00@yahoo.com> wrote in message
    >>news:3b55fec4$1@news.devx.com...
    >>>
    >>> Hi,
    >>> I have 2 independent VB applications running.
    >>> If I want to pass some parameters from prog A to prog B,
    >>> so that prog B can process the parameters and update its
    >>> display, what do I have to do in codes for these 2 programs
    >>> in order to do that?
    >>>
    >>> Hian

    >>
    >>

    >



  11. #11
    Ron Phillips Guest

    Re: passing parameters to another running VB application


    Create an ActiveX EXE project in VB. You'll get a class as the
    default object. Change the name of the class to "clsPublicInterface".
    Add some code to the class object:

    Option Explicit

    Public Function SetCaption(ByVal strArg As String)
    Form1.Caption = strArg
    End Function

    ----------

    Add a standard form to the project (Form1). Go to the project
    properties, and change the name of the project to "ActiveXTest".
    Change the Startup Object to "Sub Main". Click on the Component tab,
    and change the Start Mode to "Standalone". Add a module (Module1) to
    your project, and add some code:

    Option Explicit

    Sub main()
    Form1.Show
    End Sub

    ----------

    Now run the project. It should act like a regular EXE and show your
    Form1 window.

    ----------

    Now, open another instance of VB and create a Standard EXE project. Go
    to References and you'll see that "ActiveXTest" is listed there. Add
    a reference to that project. In the Load() event of your default
    form, add some code:

    Option Explicit

    Private Sub Form_Load()
    Dim c As New clsPublicInterface
    Call c.SetCaption("My caption")
    Set c = Nothing
    End Sub

    Now run the project, and what you'll find is that the caption of your
    ActiveX project form has just changed to "My caption", as you've
    passed it from one app to the ActiveX app.

    Hope this helps,
    Ron

    On 19 Jul 2001 21:13:03 -0700, "Hian Chew" <hschew00@yahoo.com> wrote:
    >
    >Can you give a very simple example on how to create this:
    >
    >>App1:
    >>clsPublicInterface
    >>
    >>Public Sub DoSomething()
    >>....
    >>End sub

    >
    >Thanks for the tips
    >
    >
    >
    >
    >"mrfelis" <mrfelis@yahoo.NOSPAM.com> wrote:
    >>Two choices:
    >>
    >>If you like subclassing, check into Karl's PrevInst.zip sample:
    >>
    >>http://www.mvps.org/vb/samples.htm
    >>
    >>Otherwise, make 1 or both applictions Active X. This way you can make the
    >>programs communicate directly through COM.
    >>
    >>
    >>App1:
    >>clsPublicInterface
    >>
    >>Public Sub DoSomething()
    >>....
    >>End sub
    >>
    >>
    >>App2: (Add reference to App1)
    >>set oApp1 = GetObject(,"App1.clsPublicInterface")
    >>if not oApp1 is Nothing then
    >> oApp1.DoSomething
    >>else
    >> msgbox "app1 not running"
    >>end if
    >>
    >>--
    >>~~~
    >> !ti timda I ,KO
    >>..em deppals nocaeB sivaM
    >>!draH
    >>~~
    >>C'Ya,
    >>mrfelis@yahoo!com
    >>Hian Chew <hschew00@yahoo.com> wrote in message
    >>news:3b55fec4$1@news.devx.com...
    >>>
    >>> Hi,
    >>> I have 2 independent VB applications running.
    >>> If I want to pass some parameters from prog A to prog B,
    >>> so that prog B can process the parameters and update its
    >>> display, what do I have to do in codes for these 2 programs
    >>> in order to do that?
    >>>
    >>> Hian

    >>
    >>

    >



  12. #12
    Hian Chew Guest

    Re: passing parameters to another running VB application


    So creating and activeX exe is no more different than creating a
    standard exe?

    Since this activeX exe can be run as a standalone application, in this
    case why not all the application to be created as activeX exe instead
    of standard exe? Any drawback?

    Hian Chew



    rphillips71@hotmail.com.NOSPAM (Ron Phillips) wrote:
    >
    >Create an ActiveX EXE project in VB. You'll get a class as the
    >default object. Change the name of the class to "clsPublicInterface".
    >Add some code to the class object:
    >
    >Option Explicit
    >
    >Public Function SetCaption(ByVal strArg As String)
    > Form1.Caption = strArg
    >End Function
    >
    >----------
    >
    >Add a standard form to the project (Form1). Go to the project
    >properties, and change the name of the project to "ActiveXTest".
    >Change the Startup Object to "Sub Main". Click on the Component tab,
    >and change the Start Mode to "Standalone". Add a module (Module1) to
    >your project, and add some code:
    >
    >Option Explicit
    >
    >Sub main()
    > Form1.Show
    >End Sub
    >
    >----------
    >
    >Now run the project. It should act like a regular EXE and show your
    >Form1 window.
    >
    >----------
    >
    >Now, open another instance of VB and create a Standard EXE project. Go
    >to References and you'll see that "ActiveXTest" is listed there. Add
    >a reference to that project. In the Load() event of your default
    >form, add some code:
    >
    >Option Explicit
    >
    >Private Sub Form_Load()
    > Dim c As New clsPublicInterface
    > Call c.SetCaption("My caption")
    > Set c = Nothing
    >End Sub
    >
    >Now run the project, and what you'll find is that the caption of your
    >ActiveX project form has just changed to "My caption", as you've
    >passed it from one app to the ActiveX app.
    >
    >Hope this helps,
    >Ron
    >
    >On 19 Jul 2001 21:13:03 -0700, "Hian Chew" <hschew00@yahoo.com> wrote:
    >>
    >>Can you give a very simple example on how to create this:
    >>
    >>>App1:
    >>>clsPublicInterface
    >>>
    >>>Public Sub DoSomething()
    >>>....
    >>>End sub

    >>
    >>Thanks for the tips
    >>
    >>
    >>
    >>
    >>"mrfelis" <mrfelis@yahoo.NOSPAM.com> wrote:
    >>>Two choices:
    >>>
    >>>If you like subclassing, check into Karl's PrevInst.zip sample:
    >>>
    >>>http://www.mvps.org/vb/samples.htm
    >>>
    >>>Otherwise, make 1 or both applictions Active X. This way you can make

    the
    >>>programs communicate directly through COM.
    >>>
    >>>
    >>>App1:
    >>>clsPublicInterface
    >>>
    >>>Public Sub DoSomething()
    >>>....
    >>>End sub
    >>>
    >>>
    >>>App2: (Add reference to App1)
    >>>set oApp1 = GetObject(,"App1.clsPublicInterface")
    >>>if not oApp1 is Nothing then
    >>> oApp1.DoSomething
    >>>else
    >>> msgbox "app1 not running"
    >>>end if
    >>>
    >>>--
    >>>~~~
    >>> !ti timda I ,KO
    >>>..em deppals nocaeB sivaM
    >>>!draH
    >>>~~
    >>>C'Ya,
    >>>mrfelis@yahoo!com
    >>>Hian Chew <hschew00@yahoo.com> wrote in message
    >>>news:3b55fec4$1@news.devx.com...
    >>>>
    >>>> Hi,
    >>>> I have 2 independent VB applications running.
    >>>> If I want to pass some parameters from prog A to prog B,
    >>>> so that prog B can process the parameters and update its
    >>>> display, what do I have to do in codes for these 2 programs
    >>>> in order to do that?
    >>>>
    >>>> Hian
    >>>
    >>>

    >>

    >



  13. #13
    Hian Chew Guest

    Re: passing parameters to another running VB application


    So creating and activeX exe is no more different than creating a
    standard exe?

    Since this activeX exe can be run as a standalone application, in this
    case why not all the application to be created as activeX exe instead
    of standard exe? Any drawback?

    Hian Chew



    rphillips71@hotmail.com.NOSPAM (Ron Phillips) wrote:
    >
    >Create an ActiveX EXE project in VB. You'll get a class as the
    >default object. Change the name of the class to "clsPublicInterface".
    >Add some code to the class object:
    >
    >Option Explicit
    >
    >Public Function SetCaption(ByVal strArg As String)
    > Form1.Caption = strArg
    >End Function
    >
    >----------
    >
    >Add a standard form to the project (Form1). Go to the project
    >properties, and change the name of the project to "ActiveXTest".
    >Change the Startup Object to "Sub Main". Click on the Component tab,
    >and change the Start Mode to "Standalone". Add a module (Module1) to
    >your project, and add some code:
    >
    >Option Explicit
    >
    >Sub main()
    > Form1.Show
    >End Sub
    >
    >----------
    >
    >Now run the project. It should act like a regular EXE and show your
    >Form1 window.
    >
    >----------
    >
    >Now, open another instance of VB and create a Standard EXE project. Go
    >to References and you'll see that "ActiveXTest" is listed there. Add
    >a reference to that project. In the Load() event of your default
    >form, add some code:
    >
    >Option Explicit
    >
    >Private Sub Form_Load()
    > Dim c As New clsPublicInterface
    > Call c.SetCaption("My caption")
    > Set c = Nothing
    >End Sub
    >
    >Now run the project, and what you'll find is that the caption of your
    >ActiveX project form has just changed to "My caption", as you've
    >passed it from one app to the ActiveX app.
    >
    >Hope this helps,
    >Ron
    >
    >On 19 Jul 2001 21:13:03 -0700, "Hian Chew" <hschew00@yahoo.com> wrote:
    >>
    >>Can you give a very simple example on how to create this:
    >>
    >>>App1:
    >>>clsPublicInterface
    >>>
    >>>Public Sub DoSomething()
    >>>....
    >>>End sub

    >>
    >>Thanks for the tips
    >>
    >>
    >>
    >>
    >>"mrfelis" <mrfelis@yahoo.NOSPAM.com> wrote:
    >>>Two choices:
    >>>
    >>>If you like subclassing, check into Karl's PrevInst.zip sample:
    >>>
    >>>http://www.mvps.org/vb/samples.htm
    >>>
    >>>Otherwise, make 1 or both applictions Active X. This way you can make

    the
    >>>programs communicate directly through COM.
    >>>
    >>>
    >>>App1:
    >>>clsPublicInterface
    >>>
    >>>Public Sub DoSomething()
    >>>....
    >>>End sub
    >>>
    >>>
    >>>App2: (Add reference to App1)
    >>>set oApp1 = GetObject(,"App1.clsPublicInterface")
    >>>if not oApp1 is Nothing then
    >>> oApp1.DoSomething
    >>>else
    >>> msgbox "app1 not running"
    >>>end if
    >>>
    >>>--
    >>>~~~
    >>> !ti timda I ,KO
    >>>..em deppals nocaeB sivaM
    >>>!draH
    >>>~~
    >>>C'Ya,
    >>>mrfelis@yahoo!com
    >>>Hian Chew <hschew00@yahoo.com> wrote in message
    >>>news:3b55fec4$1@news.devx.com...
    >>>>
    >>>> Hi,
    >>>> I have 2 independent VB applications running.
    >>>> If I want to pass some parameters from prog A to prog B,
    >>>> so that prog B can process the parameters and update its
    >>>> display, what do I have to do in codes for these 2 programs
    >>>> in order to do that?
    >>>>
    >>>> Hian
    >>>
    >>>

    >>

    >



  14. #14
    mrfelis Guest

    Re: passing parameters to another running VB application

    Hian Chew <hschew00@yahoo.com> wrote in message
    news:3b5a5f49$1@news.devx.com...
    >
    > So creating and activeX exe is no more different than creating a
    > standard exe?
    >


    Not exactly. An AX exe contains public classes and must be registered as a
    COM object. Also, AX EXE's must maintain binary compatibility with a
    previous version. (ie: Once you create a public function in a public class,
    the declaration of that function must remain the same. If you change the
    interface things break.)

    You can read more about AX EXE in MSDN.
    http://msdn.microsoft.com/library/en...tingolecompone
    nts.asp

    --
    ~~~
    !ti timda I ,KO
    ..em deppals nocaeB sivaM
    !draH
    ~~
    C'Ya,
    mrfelis@yahoo!com
    > Since this activeX exe can be run as a standalone application, in this





  15. #15
    mrfelis Guest

    Re: passing parameters to another running VB application

    Hian Chew <hschew00@yahoo.com> wrote in message
    news:3b5a5f49$1@news.devx.com...
    >
    > So creating and activeX exe is no more different than creating a
    > standard exe?
    >


    Not exactly. An AX exe contains public classes and must be registered as a
    COM object. Also, AX EXE's must maintain binary compatibility with a
    previous version. (ie: Once you create a public function in a public class,
    the declaration of that function must remain the same. If you change the
    interface things break.)

    You can read more about AX EXE in MSDN.
    http://msdn.microsoft.com/library/en...tingolecompone
    nts.asp

    --
    ~~~
    !ti timda I ,KO
    ..em deppals nocaeB sivaM
    !draH
    ~~
    C'Ya,
    mrfelis@yahoo!com
    > Since this activeX exe can be run as a standalone application, in this





Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center