In my WealthLab strategy I would like to use a third party .dll that communicates with an Excel spreadsheet using interop. Is there something about compiling a strategy in WealthLab that might prevent this from working?
Here are some details...
I can access this .dll with no problems from a non WealthLab winforms app.
When I access the .dll from within a WealthLab strategy, the .dll is unable to communicate with Excel. The following line of code in the .dll throws a general exception error....
try
CODE:
Please log in to see this code.
(see key namespaces listed below)
It seems that for some reason it cannot access the running object table (rot). Is there anything you can think of that would cause this problem?
Thanks,
Tim
The key namespaces that the 3rd party .dll uses are...
CODE:
Please log in to see this code.
My system specs are
Windows 7
WealthLab 6.6 (64 bit)
Excel 13 (64 bit)
Microsoft Access Database Engine _64 2010
Size:
Color:
According to MSDN, Marshal.GetActiveObject throws a general
COMException. What does it say in particular?
Size:
Color:
COMException is The object was not found.
Not very useful. Anyway, Excel is definitely running and I created a non WealthLab winforms app that I can run and it can find "Excel.Application" every time.
Size:
Color:
Size:
Color:
Size:
Color: