Excel COM Object

This is the error I am recieveing
An exception occurred when instantiating a Com object.
The cause of this exception was that:
coldfusion.runtime.com.ComObjectInstantiationException: An
exception occurred when instantiating a Com object..
I have seen others having this same issue, but a solution
have never been supplied.

The com pool can be accessed with admin priveleges in:
Start Menu > Programs > Administrative Tools >
Component Services
drill down to COM+ Applications and checked the icon for your
COM is rotating...
If it's not - right-click and select Start
If it is - right click and select 'Shut Down', then
right-click and select 'Start'

Similar Messages

Close Excel com object without saving changes?

Hi, I am trying to write a script which opens each of 31 excel workbooks, retrieves a value from a cell, and closes each workbook after retrieving.
My code so far:
$day=1
$excel = New-Object -ComObject Excel.Application
$excel.Visible=$True
$workbook= $excel.Workbooks.Open("C:\Path|to\File\1_"+$day+"_14.xlsx")
$workbook.sheets.item(1).activate()
$WorkbookTotal=$workbook.Worksheets.item(1)
$value = $WorkbookTotal.Cells.Item(7,13)
$value.Text #this should give you back the Value in that Cell
$excel.close()
My problem is that when the code hits the $excel.close() method, the file stays open, and prompts for saving changes. I don't know why it thinks there are changes, but what I want is to close the workbook without saving changes.
I've just closed 44 open browser tabs, and have tried many things over the last hour, but can't seem to get this one.
If anyone has any advice on how to do this, it would be greatly appreciated!
Thanks,
Kevin

Hi,
Please replace below code:
$excel.close()
with
$workbook.close($false)
$excel.quit()
Hope this helps.
Regards,
Yan Li
Regards, Yan Li

Excel COM object calls break with Office 2013 upgrade on 64-bit OS?

Out of the 1000+ computers in the company mine is the only one running 64-bit windows 7. I have noticed that when i try to run a small DLL i created to convert Excel files to Tab Delimited files it is crashing only on my computer.
I have debugged the source code and found that there is no real exception being thrown except a popup does appear in the background stating "We're sorry, but Excel has run into an error that is preventing it from working correctly. Excel will need to
be closed as a result. Would you like us to repair now? [Repair Now][Help][Close]"
If i open excel via the main application this same popup comes up and when i click repair excel closes. when re-opened Excel re-activates and then works fine.
here is a sample of my (VERY simple) code which has worked for years on office 2007 with 64-bit OS:
Dim excelPath As String = "C:\test.xlsx"
Try
objXL = CreateObject("Excel.Application")
With objXL.Application
.displayalerts = False
.Visible = False
.workbooks.Open(excelPath)
.Workbooks(ExcelFileName).SaveAs(csvPath & csvFileName, Excel.XlFileFormat.xlCurrentPlatformText, , , , , Excel.XlSaveAsAccessMode.xlNoChange, , , , , )
.workbooks(csvFileName).Close(csvPath & csvFileName, savechanges:=True)
End With
Catch ex2 As Exception
Throw ex2
Finally
objXL.Quit()
objXL = Nothing
End Try
I have isolated the exact line that is causing the exception to be thrown...
.Visible = False
Why would hiding the Excel UI cause an error of "We're sorry, but Excel has run into an error that is preventing it from working correctly" to be displayed?
If i remark out this line then the application seems to work properly for me...

That I do not know. Do you have another machine where Office 2013 is installed, and where you can test? It could be system configuration issue, could be a change in the application behavior or a difference between 32-bit and 64-bit. You are updating
at least a couple of generations of software and now running in a 64-bit environment so there is always the potential for changes in behavior and software defects.
Unfortunately, I do not have Office 2013 64-bit installed so I cannot test this scenario.
You could also try posting to the
Excel for Developers forum to see if anyone has encountered the same issue when using Excel automation.
Paul ~~~~ Microsoft MVP (Visual Basic)

Excel COM object in Unix Server

We generated the Excel file with Macros in NT server with Excel Installed. Is there is any way to achieve this in Unix Server?
Thanks in Advance
Ayyanar

There are a couple of ways to generate Excel files, regardless of the operating system. If your version of Excel supports the Excel XML file format, then you can use PeopleCode to generate text based Excel XML files. For this approach, you usually create a template from an Excel XML file and then insert placeholders for content (usually in the form of XSL, but it could be %Bind(:n) in an HTML Definition).
Another approach I have used is [Apache POI|http://poi.apache.org/].
I don't work with XMLPublisher, but it may support Excel output as well.

Error when instantiating a Com( EXCEL.APPLICATION) object in WINDOWS XP

Hi,
I am using coldfusion MX7 and OS is WindowXP. I am using COM
object with Excel.Application for my program. but it is giving the
below error. But same program is working in Window Profesional.
ERROR IS:
An exception occurred when instantiating a Com object.
The cause of this exception was that: AutomationException:
0x80080005 - Server execution failed. Note that Windows 95 does not
support automatic launch of a server, it must be running already.
The error occurred in
C:\CFusionMX7\wwwroot\XXX\report_top20.cfm: line 15
13 : t1=now();
14 : path=GetDirectoryFromPath(ExpandPath("*.*"));
15 : xl=CreateObject("COM", "Excel.Application");
16 : wbks=xl.workbooks;
17 : tmp=wbks.open(path & "top20_template.xls");
Plz help me.
Reagrds,
DRA.

Hi,
If possible, would you please share your Excel file with us, you can upload it to a file sharing site(Like OneDrive), and then share the link with us. Also please take a look of this article:
http://support.microsoft.com/kb/178510
For the warning message, It means that in Excel 2010 and Excel 2007, you can use special effects, such as transparent shadows that are not supported in Excel 97-2003. The special effects will be removed. In the Compatibility Checker, click
Find to locate the objects that have special effects applied so that you can remove those effects as needed.
Wind Zhang
TechNet Community Support

On cleanuing up COM object when using Microsoft.Office.Interop.Excel

When using Microsoft.Office.Interop.Excel the COM objects that are created by the code must be released using System.Runtime.InteropServices.Marshal.ReleaseComObject().
Most of the time it's pretty clear when a new COM object is created such as:
Excel._Application excelApp = null;
Excel._Workbook wb = null;
Excel._Worksheet ws = null;
Excel.Range newRange = null;
try
// four COM objects are created below
excelApp = new Excel.Application();
wb = excelApp.Workbooks.Add();
ws = (Excel.Worksheet)wb.Worksheets.Add();
newRange = (Excel.Range)ws.Range["A1","A30"];
// do these line of cod create new COM object?
newRange.Font.Bold = true;
newRange.Borders.Color = borderColor;
finally
if (excelApp != null) Marshal.ReleaseComObject(excelApp)
if (wb != null) Marshal.ReleaseComObject(wb)
if (ws != null) Marshal.ReleaseComObject(ws)
if (newRange != null) Marshal.ReleaseComObject(newRange)
In the above code I create four COM objects in the first part that need to be released when I'm finished with them. But it's not clear if the other two lines of code create a new COM object or not. If they do then my code needs to look more
like this:
Excel._Application excelApp = null;
Excel._Workbook wb = null;
Excel._Worksheet ws = null;
Excel.Range newRange = null;
Excel.Font fnt = null;
Excel.Borders bds = null;
try
// four COM objects are created below
excelApp = new Excel.Application();
wb = excelApp.Workbooks.Add();
ws = (Excel.Worksheet)wb.Worksheets.Add();
newRange = (Excel.Range)ws.Range["A1","A30"];
// do these line of cod create new COM object?
fnt = newRange.Font
fnt.Bold = true;
bds = new newRange.Borders;
bds.Color = borderColor;
finally
if (excelApp != null) Marshal.ReleaseComObject(excelApp)
if (wb != null) Marshal.ReleaseComObject(wb)
if (ws != null) Marshal.ReleaseComObject(ws)
if (newRange != null) Marshal.ReleaseComObject(newRange)
if (fnt != null) Marshal.ReleaseComObject(fnt)
if (bds != null) Marshal.ReleaseComObject(bds)
How can I tell if getting a property creates a new COM object or not?

Thank you for your replay but I do understand that the font object is a COM object. What I'm trying to figure out is if a NEW object is created each time I access the font member of a Range object and if I need to call
Marshal.ReleaseComObject on the font object after using it.
Most member object of an object are a single instance and each time you access the member you simply get the pointer to that instance. For example:
using(DataTable dt = new DataTable("Some Table Name"))
PropertyCollection ep1 = dt.ExtendedProperties;
PropertyCollection ep2 = dt.ExtendedProperties;
if (Object.ReferenceEquals(ep1,ep2)) Console.WriteLine("They are the same object");
else Console.WriteLine("They are different objects");
The output will be: They are the same object
On the other hand this:
Excel._Application excelApp = new Excel.Application();
Excel._Workbook wb = excelApp.Workbooks.Add();
Excel._Worksheet ws = (Excel.Worksheet)wb.Worksheets.Add();
Excel.Range newRange = (Excel.Range)ws.Range["A1","A30"];
// do these lines of code create new COM object?
Excel.Font ef1 = newRange.Font;
Excel.Font ef2 = newRange.Font;
if (Object.ReferenceEquals(ef1,ef2)) Consloe.WriteLine("They are the same object");
else Consloe.WriteLine("They are different objects");
The output will be: They are different objects
It looks like each time I access the font member I get a new object. I suspect that is not the case and what I am getting is two pointers to the same object and the reference counter is incremented by one.
So really the question is what happens to the font member object of the Range object when the range object is released. I assume the font member will be released along with the Range object ever if the font object has a reference count greater then
0.
If I am correct in my assumption then I can access the font member object as much as I need to without worrying about releasing it.
I have been reading a lot about working with COM and the need to use Marshal.ReleaseComObject and there does seem to be a lot of disagreement and even confusion on the
mater about when and if COM objects need to be explicitly released.

Invalid method "Save As" from Excel application object

I have Windows 2000 and Excel 2002 installed on my machine.
I down loaded "renamed Excel 2000 workbook.vi" from NI website. Relinked ref num to Excel application object but get the error of invalid method (Save As). Tried to relink invoke node to Save As by selecting method from drop down menu. However this method is not on the list. Tried other excel objects but can not find "Save As" method. Has this been removed/moved?

I was able to correct the error by relinking the Workbooks->Open to Open. This changes the subsequent Invoke Node from IAppEvents to _Workbook. There you will find the Save As method.
Michael
www.abcdefirm.com
Michael Munroe, ABCDEF
Certified LabVIEW Developer, MCP
Find and fix bad VI Properties with Property Inspector

How to Use AccessibleObjectFromWindow API in VBA to Get Excel Application Object from Excel Instance Window Handle

I need to get the Excel.application object from a window handle using AccessibleObjectFromWindow. I can't seem to make the code work. First, I successfully search for the XLMAIN windows. Then, when I get a handle, I execute the AccessibleObjectFromWindow
function. It seems to return a value of -2147467262 in all cases. Therefore, I believe that it is returning an error value. I can't figure out how to determine the meaning of this value.
If it is an error value, I believe that one or more arguments are in error. My best guess at present is that the GUID argument is incorrect. I have tried two GUID values: {00020400-0000-0000-C000-000000000046} and {90140000-0016-0409-0000-0000000FF1CE}.
I have seen both used in conjunction with OBJID_NATIVEOM. Neither one seems to work. I really would prefer not to use the second one as it has an Excel major and minor version number. I would hate to have to change this code, if a new minor version appeared.
The attached code has been commented to show which parts have been shown to work and which not. I'm at my wits end and really need help.
Thanks
'This module is located in Access 2010, but this is an Excel question.
Option Compare Database
Option Explicit
' Module-Level Declarations
'The GetDesktopWindow function and FindWindowEx function work just fine.
Public Declare Function GetDesktopWindow Lib "user32" () As Long
Public Declare Function FindWindowEx Lib "user32" Alias "FindWindowExA" _
(ByVal hWnd1 As Long, _
ByVal hWnd2 As Long, _
ByVal lpsz1 As String, _
ByVal lpsz2 As String) _
As Long
'I'm not getting the expected output from this function (see below)
Private Declare Function AccessibleObjectFromWindow& Lib "oleacc.dll" _
(ByVal hwnd&, _
ByVal dwId&, _
riid As GUID, _
xlwb As Object)
Type GUID
lData1 As Long
iData2 As Integer
iData3 As Integer
aBData4(0 To 7) As Byte
End Type
Function ExcelInstances() As Long
' Procedure-Level Declarations
' Value of OBJID_NATIVEOM verified by checking list of Windows API constants _
on this site: http://www.lw-tech.com/q1/base.htm
Const OBJID_NATIVEOM = &HFFFFFFF0
Dim hWndDesk As Long 'Desktop window
Dim hWndXL As Long 'Child window
Dim objExcelApp As Object 'Final result wanted: Excel application object
'Following variable (xlapp) to be set by AccessibleObjectFromWindow function
Dim xlapp As Object
Dim IDispatch As GUID 'GUID used in call to AccessibleObjectFrom Window function
'Set up GUID to be used for all instances of Excel that are found
Dim tmp1 As Variant 'Return value from AccessibleObjectFromWindow
' Executable Statements
SetIDispatch IDispatch
IDispatch = IDispatch
'Get a handle to the desktop
hWndDesk = GetDesktopWindow 'This seems to work
Do
'Get the next Excel window
'The following statement seems to work. We are finding and counting _
correctly all the instances of Excel. hWndXL is non-zero for each _
instance of Excel
hWndXL = FindWindowEx(GetDesktopWindow, hWndXL, "XLMAIN", vbNullString)
'If we got one, increment the count
If hWndXL > 0 Then
'This works. We correctly count all _
instances of Excel
ExcelInstances = ExcelInstances + 1
'Here is the problem. The following statement executes and returns a value of _
-2147467262. xlapp, which is passed by reference to AccessibleObjectFromWindow, _
is set to nothing. It should be set to the object for Excel.application. _
I believe that this value is not an object. I tried to reference tmp1. in the _
immediate window. There was no Intellisense.
'I think that the function in returning an error value, but I can't figure _
out what it is. I believe that AccessibleObjectFromWindow returns error _
values, but I don't know where to find their values so I can interpret the _
function's results.
'As best I can tell, the hWndXL parameter is correct. It is the handle for _
an instance of Excel. OBJID_NATIVEOM is set correctly (see constant declaration _
above). xlapp is passed by reference as a non-initialized object variable, which _
will be set by AccessiblObjectFromWindow. IDispatch may be the problem. It is set _
as shown below in the procedure SetIDispatch(ByRef ID As GUID). This procedure _
appears to work. I can see that IDispatch is set as I intended and correctly _
passed to AccessibleObjectFromWindow.
tmp1 = AccessibleObjectFromWindow(hWndXL, OBJID_NATIVEOM, IDispatch, xlapp)
'Need to write code to test tmp1 for error. If none, then set objExcelApp = _
object. Also, I exect xlapp to be set to Excel.application
End If
'Loop until we've found them all
Loop Until hWndXL = 0
End Function
Private Sub SetIDispatch(ByRef ID As GUID)
'Defines the IDispatch variable. The interface _
ID is {90140000-0016-0409-0000-0000000FF1CE}.
'NOT USING {00020400-0000-0000-C000-000000000046}, _
which could be the problem
'9 is release version - first version shipped (initial release)
'0 is release type - retail/oem
'14 is major version
'0000 is minor version
'0016 is product ID - MS Excel 2010
'0409 is language identifier - English
'0 is x86 or x64 - this is x86
'000 reserved
'0 is debug/ship
'000000FF1CE is office family ID
With ID
.lData1 = &H90140000
.iData2 = &H16
.iData3 = &H409
.aBData4(0) = &H0
.aBData4(1) = &H0
.aBData4(2) = &H0
.aBData4(3) = &H0
.aBData4(4) = &H0
.aBData4(5) = &HF
.aBData4(6) = &HF1
.aBData4(7) = &HCE
End With
End Sub
DaveInCalabasas

I don't think you can return a reference to Excel's main window like that as you are attempting to do.
Ref:
http://msdn.microsoft.com/en-us/library/windows/desktop/dd317978(v=vs.85).aspx
It's relatively straightforward to return any workbook's window in any given instance, and in turn it's parent Excel app. Try the following and adapt as required (and include error handling) -
Option Explicit
Private Declare Function FindWindowEx Lib "User32" Alias "FindWindowExA" _
(ByVal hWnd1 As Long, ByVal hWnd2 As Long, ByVal lpsz1 As String, _
ByVal lpsz2 As String) As Long
Private Declare Function IIDFromString Lib "ole32" _
(ByVal lpsz As Long, ByRef lpiid As GUID) As Long
Private Declare Function AccessibleObjectFromWindow Lib "oleacc" _
(ByVal hWnd As Long, ByVal dwId As Long, ByRef riid As GUID, _
ByRef ppvObject As Object) As Long
Private Type GUID
Data1 As Long
Data2 As Integer
Data3 As Integer
Data4(7) As Byte
End Type
Private Const S_OK As Long = &H0
Private Const IID_IDispatch As String = "{00020400-0000-0000-C000-000000000046}"
Private Const OBJID_NATIVEOM As Long = &HFFFFFFF0
Sub test()
Dim i As Long
Dim hWinXL As Long
Dim xlApp As Object ' Excel.Application
Dim wb As Object ' Excel.Workbook
hWinXL = FindWindowEx(0&, 0&, "XLMAIN", vbNullString)
While hWinXL > 0
i = i + 1
Debug.Print "Instance_" & i; hWinXL
If GetXLapp(hWinXL, xlApp) Then
For Each wb In xlApp.Workbooks
Debug.Print , wb.Name
Next
End If
hWinXL = FindWindowEx(0, hWinXL, "XLMAIN", vbNullString)
Wend
End Sub
'Function GetXLapp(hWinXL As Long, xlApp As Excel.Application) As Boolean
Function GetXLapp(hWinXL As Long, xlApp As Object) As Boolean
Dim hWinDesk As Long, hWin7 As Long
Dim obj As Object
Dim iid As GUID
Call IIDFromString(StrPtr(IID_IDispatch), iid)
hWinDesk = FindWindowEx(hWinXL, 0&, "XLDESK", vbNullString)
hWin7 = FindWindowEx(hWinDesk, 0&, "EXCEL7", vbNullString)
If AccessibleObjectFromWindow(hWin7, OBJID_NATIVEOM, iid, obj) = S_OK Then
Set xlApp = obj.Application
GetXLapp = True
End If
End Function
Note as written if an instance does not have any loaded workbooks a reference will not be returned (though a workbook can be added using DDE, but convoluted!)
FWIW there are two other very different approaches to grab all running Excel instances though something along the lines of the above is simplest.
Peter Thornton

Help and some explanation how to get a Microsoft.Office.Tools.Excel.Worksheet host item that extends the functionality of the current Microsoft.Office.Interop.Excel.Worksheet object

Hello,
I would use some help and more info about how to get host object that extends the functionality of my current Interop.Excel.Worksheet object. I read this artical: https://msdn.microsoft.com/en-us/library/ee794671.aspx where I can call this function
GetVstoObject to get host object. But I see that here I need to pass the Globals.Factory object as second parametar. Can someone give me more details about that parameter and how to access it? I would like to get host object so I can access extension
property, since my interop excel worksheet doesn't have it.
I am using Visual Studio 2013 for developing Excel addin. Using Excel 2010.
Thanks in advance for help.
Regards,
Zeljka

Hi Zeljka,
>>I am using the Microsoft Office PIAs, so my question is how to access this automatic generated class Globals in my case? <<
Sorry, I am not able to understand the application you were developing exactly. From the orgnal post, you were developing an application level add-in, however based on the description above, it seems that you were building an console or Windows form application
to automate Office application.
If you were developing Office automation, the host item can't work for this secnario since it should run under the VSTO runtime.
If I misunderstood, please feel free to let me know.
Regards & Fei
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Problem calling COM Object on Windows Server 2008 x64

Hi,
We are using 32 bits COM object called in Coldfusion page on 32 bits OS. It works fine since few years.
Now we need to use it on x64 Windows Server 2008 and 64bits IIS.
As I 've seen (http://www.coldfusionjedi.com/forums/messages.cfm?threadid=87869C67-B1 9B-288F-F32B6E8BAB3228CA ),a 64 bits process can only call 64 bits DLL.
So we created a 64 bits Wrapper like this : http://www.dnjonline.com/article.aspx?id=jun07_access3264
But calling 64 bits COM Object still raises the same error (" The cause of this exception was that: java.lang.RuntimeException: Can not use native code: Initialisation failed") whereas it works fine with a 64 bits executable created in .NET for example.
Is there a known issue about this subject?
Sorry for english , I'm a french developper.
Thanks in advance.

Can somebody please share the solution for this issue?
I am facing similar issue with Windows 2012 R2 x64 OS and Excel 2007(32-bit) combination.
I tried couple of things like Excel is able to Open an existing workbook on my system but fails to
create a new Workbook as done by invoking the "Add" command. It fails with Error 800a03ec.
I tried creating the two folders i.e. C:\Windows\SysWOW64\config\systemprofile\Desktop & C:\Windows\system32\config\systemprofile\Desktop, but could not get it working.

Accessing COM Objects provided by an EXE server

Hello,
I need to control an application through COM. I did this before with Excel and other software and used LabView's ActiveX functions.
But this time I can't find the object I need when I browse the type library.
The COM server actually is registered. But it's an "EXE Server" (I used "COM Explorer" to browse all registered COM objects - and the one I need is listed under EXE Servers).
Is there any possibility to gain access to this interface?
Thanks!
Regards,
Robert

Hi Robert,
there is not really a difference between ActiveX object and COM object.
All COM objects (ActiveX objects) should be accessible.
If you can't see the object, but you know that you had register it, there are only two possibilities:
1) Something is wrong with the object -> it is not really standard
2) You can try to browse manually to the object.
Use the "Browse" Button (see Browse.jpg) and select the object manually.
If that doesn't work, there must be something wrong with the object.
Best regrads
Dippi
Attachments:
Browse.jpg ‏29 KB
Select Object.jpg ‏163 KB

CSA instantiating Excel COM add-in on wrong thread

Hello,
we sell an add-in to Excel, which is a COM object registered with
threading model "single". When Cisco Security Agent is installed, it
looks like our COM object is being instantiated not from the main
thread but a different thread, which is illegal. Is there anyone from
Cisco or close to them who can comment on that? I do not have Cisco
Security Agent myself, and have not managed to convince Cisco to give
me a test version.
Thanks for help,
Arno

Hi SivaPrasanth,
Welcome to post in MSDN forums!
What alert did you get?
I made an Excel add-in in my solution, and then loaded a local html file, by default, the Webbrowser didn't give me any alerts. But when I navigated to some websites with javascript errors in the page, it then give me an alert, but no flickering after I
clicked Yes.
Is it the same as yours?
I think javascript errors might cause the flickering, please check if this problem remains if you open the htm page in IE browser.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

How sharing a COM object with severeal test dlls in teststand

I have several tests (dlls) accessing a DAQ board (not VI compliant) thanks to a COM object. I would like to keep one instance of this object, passing its reference to each test dll, instead of creating one in each test. How can I do that with TestStand?

You can do one of two things to store a reference to the COM object in the context of TestStand so that you can pass it to successive steps in order for them to all use the same object instance.
First, if you create the object in TestStand with an ActiveX Automation Adapter step, the method call to instantiate the object should return a reference to the object. If you designate an activex reference type local variable as the property to receive the reference during the creation operation, you should be able to pass this into methods that use IDispatch* parameters, or you can use the TestStand API to access the TestStand variable instead.
The second scenario is very similar, in that if you don't create the object in TestStand but inside of a dll instea
d, you can simply pass the parameter back from a function into a TestStand activex reference property variable or use the TestStand API inside of the dll to set the value of an activex reference property to the IDispatch of the object.
To better understand how to use the ActiveX Automation Adapter and ActiveX Reference Variable Types, look at Chapter 13 of the TestStand User Manual under the section entitled "ActiveX Automation Adapter". I have also attached an example to this post that uses the ActiveX Automation Adapter and ActiveX reference datatype in a sequence that writes data to a Microsoft Excel spreadsheet and generates a chart from the data.
Jason F.
Applications Engineer
National Instruments
www.ni.com/ask
Attachments:
Write_Table_to_XL_and_Create_Chart.seq ‏53 KB

How can I use a COM object that does not have a type library?

Hello,
I've created a com server in python for which I do not have a type library. I am able to call functions for this application in Python, TCL, I'm sure VB, etc. without the type library.
Must I have a type library registered to use this COM object with Labview? I was hoping I could simply supply the name to the refnum (or the GUID) then call functions by passings strings to the invoke node. This does not seem to be possible - am I missing something?
In the event that I cannot use a com server without a type library. Any recommendataions on how to create one? I'm wondering if I can use the same GUID and create a shell in LabWindows which generates the IDL/TBD file I need for Labview to see my
com server.
Any help is greatly appreciated.
73,
Timothy

Timothy Toroni wrote:
> Thanks for the info, however their example is labview server and
> python client. I'm going the other way. It's good to know about
> LabPython though...
>
> As of now, it seems to be there is no way to use a COM object without
> a type library from inside LabView.
Yes that is true. LabVIEW needs that to configure the Property and
Methode Nodes correctly. Otherwise it would need to have a special
Property and Method Node with a configuration dialog similar to the Call
Library Node, but a LOT more complicated. Not sure many people could
make use of that, and it would be a very tiring experience trying to get
things setup in that way, by going through the edit, test, and crash
cycle over and over again.
Rolf Kalberm
atter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

How can I call a COM object from a PL/SQL CODE

Hi everyone,
Does anyone know how to call a COM object from a stored procedure in oracle.
a sample of code
please help,
Hilaire

Are you familiar with external procedures? Basically, you can expose functions exported by a shared library (i.e. a DLL on Windows) to the Oracle database. My assumption is that you'd probably need to write a wrapper DLL around the COM object, since I believe you can only pass fundamental data types back and forth (i.e. no object references). You'd expose the method(s) of that wrapper DLL to the database via external procedures.
Justin
Distributed Database Consulting, Inc.
www.ddbcinc.com/askDDBC

Excel COM Object

Similar Messages

Maybe you are looking for