VB6 application automation question

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Shuttermutt
    #1

    VB6 application automation question

    Good day, all! I'm wondering if it's possible to write two applications
    so that they can each compile to their own EXE, but one application can
    manipulate the objects on the other application. For example...

    App_A
    ---
    ' This app has a form with a text box
    txtAddress

    App_B
    ---
    ' This app can access the methods and properties of App_A's text box
    App_A.txtAddres s.Text = "foo"

    No? Perhaps if it looked like this...

    App_A (ref:DLL)
    ---
    ' This app has a form with a text box and references a DLL
    txtAddress

    DLL
    ---
    // This DLL can somehow drive App_A
    clsAppA
    {
    modifyAddress() ;
    }

    App_B (ref:DLL)
    ---
    ' This app has a reference to the same DLL and drives App_A via that
    DLL's class(es)
    a = new clsAppA();
    a.modifyAddress ("foo");

    Okay, this is really awful pseudocode, but hopefully you'll get the
    idea. What little I've found on this makes me believe it's referred to
    as out-of-process automation. My problem is that I can't find any
    example of how it can be done in VB6 (if at all).

    Again, what I'm really wanting to do is to call functions, modify
    objects, and generally act as if App_B is a part of App_A without the
    need to compile the code in to App_A.

    Any kick in the right direction would be sincerely appreciated!

    'Mutt

    Tags: None
    • Slaatje
      #2
      Re: VB6 application automation question

      Check your helpfile: MDI or DDE

      Shuttermutt heeft geschreven in bericht ...[color=blue]
      >Good day, all! I'm wondering if it's possible to write two applications
      >so that they can each compile to their own EXE, but one application can
      >manipulate the objects on the other application. For example...
      >
      >App_A
      >---
      >' This app has a form with a text box
      >txtAddress
      >
      >App_B
      >---
      >' This app can access the methods and properties of App_A's text box
      >App_A.txtAddre ss.Text = "foo"
      >
      >No? Perhaps if it looked like this...
      >
      >App_A (ref:DLL)
      >---
      >' This app has a form with a text box and references a DLL
      >txtAddress
      >
      >DLL
      >---
      >// This DLL can somehow drive App_A
      >clsAppA
      >{
      > modifyAddress() ;
      >}
      >
      >App_B (ref:DLL)
      >---
      >' This app has a reference to the same DLL and drives App_A via that
      >DLL's class(es)
      >a = new clsAppA();
      >a.modifyAddres s("foo");
      >
      >Okay, this is really awful pseudocode, but hopefully you'll get the
      >idea. What little I've found on this makes me believe it's referred to
      >as out-of-process automation. My problem is that I can't find any
      >example of how it can be done in VB6 (if at all).
      >
      >Again, what I'm really wanting to do is to call functions, modify
      >objects, and generally act as if App_B is a part of App_A without the
      >need to compile the code in to App_A.
      >
      >Any kick in the right direction would be sincerely appreciated!
      >
      >'Mutt
      >[/color]


        Comment

        • J French
          #3
          Re: VB6 application automation question


          Look into AX Exes

          - that sounds like what you are after

          On Thu, 04 Sep 2003 23:18:19 GMT, Shuttermutt <shuttermutt@no spam.com>
          wrote:
          [color=blue]
          >Good day, all! I'm wondering if it's possible to write two applications
          >so that they can each compile to their own EXE, but one application can
          >manipulate the objects on the other application. For example...
          >
          >App_A
          >---
          >' This app has a form with a text box
          >txtAddress
          >
          >App_B
          >---
          >' This app can access the methods and properties of App_A's text box
          >App_A.txtAddre ss.Text = "foo"
          >
          >No? Perhaps if it looked like this...
          >
          >App_A (ref:DLL)
          >---
          >' This app has a form with a text box and references a DLL
          >txtAddress
          >
          >DLL
          >---
          >// This DLL can somehow drive App_A
          >clsAppA
          >{
          > modifyAddress() ;
          >}
          >
          >App_B (ref:DLL)
          >---
          >' This app has a reference to the same DLL and drives App_A via that
          >DLL's class(es)
          >a = new clsAppA();
          >a.modifyAddres s("foo");
          >
          >Okay, this is really awful pseudocode, but hopefully you'll get the
          >idea. What little I've found on this makes me believe it's referred to
          >as out-of-process automation. My problem is that I can't find any
          >example of how it can be done in VB6 (if at all).
          >
          >Again, what I'm really wanting to do is to call functions, modify
          >objects, and generally act as if App_B is a part of App_A without the
          >need to compile the code in to App_A.
          >
          >Any kick in the right direction would be sincerely appreciated!
          >
          >'Mutt
          >[/color]

            Comment

            Previous template Next
            Working...