Accessing compiled VI`s via VBA

[Ben]

I confess that I have not studied every word spoken in this discusion.

I do not think we have proven if the issue is with LV's activeX service or VBA's access to the same.

Have you tried accessing you exe from a LV app?

Just asking dumb questions that may inspire good answers.

Ben

[Dave_Karon]

I am having a very similar problem.  I have 4 ActiveX enabled LV built executables that I am launching from VBA code run from (and tied to) an Excel sheet.

The four apps are built in either LV 8.5.1 (one of them that does DAQ) or LV 8.6.1 (the other three that do ethernet comms and reading from or writing to DataSocket).

They've been running fine under Win2K ( with O2K) and WinXP (with Office 2007), but when installed and run (or trying to) under Win7 I get that error 429 .....

Also cwds gave me problems, but when I configured it to run as administrator and set the folder in which it resides to be a trusted location, cwds now behaves. 

( I didn't try only one of those)

I tried converting one of those LV projects to LV 2010SP1 andbuilding it, and it behaves exactly the same... "Error 429, ActiveX component can't create object"

I have an active service reequest going, but I thought I'd post this and see if anyone else has seen this behavior.

thanks in advance.

DaveK