title: OLE Automation and interacting with another VBE / VBA IDE
body: <p>I am familiar with OLE Automation and controlling other applications from a given VBA IDE / VBE (particularly Excel's VBE). While I know it's possible to use the SendKeys method as a way to essentially accomplish what I am trying to do, I feel it can be unreliable in certain situations (not to mention a little sloppy).</p>
  
  <p>In a nutshell, I am attempting to write a VBA module to a text file from within Excel (already figured this one out) and then have a target application's VBA IDE import the module and execute the code.</p>
  
  <p>My primary reasoning for this is that the reference libraries available to Excel in regards to said target application have limitations (while, as one would expect, the target application's VBA IDE has much more properties and methods to work with as its reference libraries are specific to the application itself, for obvious reasons).</p>
  
  <p>Any thoughts on how to best accomplish this?  </p>
  
  <p>Would it be better to just create a custom COM reference or tweak and existing one (I would assume this is fairly difficult as I am not familiar with C# or Visual Studio)?</p>
  
  <p>(Note: In case you were wondering, I am working with Reflection Sessions (IBM, for Windows), and have pretty extensive exposure to the primary COM I am working with (EXTRACOM). Within the Reflection Sessions VBE there are methods such as <code>.GetFieldText</code> (which will return the entire field name regardless of where the application cursor is placed on a given field. This can be much more useful than EXTRACOM's <code>.GetString</code> which requires the programmer to specify field length first and cursor position). Another property method: <code>.GetFieldColor</code> (which will return a numerical code for a field's color, a property/method that EXTRACOM (Excel's reference file for Reflection) lacks.</p>