![com api vba interface com api vba interface](http://ww3.cad.de/foren/ubb/uploads/passiel/VB_Api_Problem.jpg)
![com api vba interface com api vba interface](https://images-na.ssl-images-amazon.com/images/I/51Ly94JaYYL._AC_UL600_SR600,600_.jpg)
This of course leads me back to the original problem of finding this workbook and populating it with my data from my current VBA workbook. Looks like I am back to using the Shell command version to open the 2nd instance of Excel. '''' SHELL "C:\Program Files\Microsoft Office\Office12\EXCEL.EXE """ & sWorkbookToOpen & """"
#Com api vba interface code
'''' 'Commented out to test out the opening of 2nd instance of Excel and hope code proceeds onward 'Open current file in the newly created version of Excel Set xlT2App = CreateObject("Excel.Application") Need to Launch T2APITool in its own Instance '131015 FM3 rev6.3a Because the T2APITool locks excel access due to prompts _Īll of Excel remains locked and the code will not progress until _īuttons are pushed. Heck, I wish I did not need the second instance of Excel and get the two combined into a single instance again, however, there does not seem to be a way to do this.Īwe man - This is killing me - So I tried to start another instance of excel - and due to the initial auto connect of the workbook, the code locks up tighter than a water rats backside until the window is acknowledged. So how can I connect to the opened second instance of Excel and place my values into it. Problem now is I am trying to send values from my Excel VBA program in one instance of Excel to another instance of Excel that is running the VB.NET workbook.
#Com api vba interface windows
NET workbook from a VBA programmed shell command and open the VB.NET workbook in a second instance of Excel, then use WINDOWS API to click the OK button. This VBA code, however, does not work for the VB.NET creation, and I assume it is because VBA and VB.NET do not mix and the code simply gets ignored So my first solution - Application.DisplayAlerts = False. Thus, already a problem because the code locks up till the user pushes OK. When it does this it prompts the user "that it is connecting to the application" then needs a user input to push the OK button. When it opens, it auto connects to the rigorous app. BUT I have a working Excel VB.NET workbook that interfaces the rigorous app and if I can populate my VBA workbook information into that Excel file, run the VB.NET workbook app, and read back the results into my VBA program then life would be golden. Of course there is no code seen, due to it being in VB.NET and written using Visual Studio.NET. OR IS IT, Bwahahahaha!Īs part of the Rigorous Program install, they deliver a API Excel Tool Workbook. So my code is still out of luck to communicate to the program. VBA and VB.NET do not play well with one another and the VBA Interopt would require VisualStudio.NET as well as learning VB.NET. However, recently a rigorous program that calculates the same values but with more accuracy as I do in my VBA workbook has added a API to its install. I have a simple Excel VBA Workbook program that has worked fine up till now just using its internal calculations. OK so this is a new one for me and I always seem to get the fun stuff. My First Post but trust a freaking long time user.