Error 1003 when compiling...

[Joe_Guo]

what are the properties you are having trouble with? Like I said in the previous post, even though some properties or methods (for example, OpenFile) have been changed in the newer version, these properties and methods are backward compatible. Try to relink the properties and methods that have problems on your devlopment machine (97) and build the appilcation. If you can successfully build the application, test it under the target machine (03). Luck may well be on your side.

-Joe

[Joe_Guo]

---

That's interesting... do you have the VBA code run automatically when the user loads the worksheet in Excel?

---

you can save the VBA code in text files or in a string constant and load it (using the Run Macro VI or Insert VBA object) whenever you want it (of course after Excel startup).

---

When you say "In the code I can then check the target Excel version"--you mean in the VBA code correct?

---

Yes, inside the VBA code, but you can also done it in Labview and load different VBA code depends on the Excel version.

---

While the typical use for Excel is probably to export data, I am actually using it to import configuration data since it happens to make importing columnated tables really simple. You can make them look like whatever you want also since the input functions will read all the text and ignore the formatting... makes for a good user interface.

---

do you mean the tabular data (ASCII format)? It's not hard to write a similar function/interface in Labview. Besides, you'll not be limited by the amount of data you can import in labview.

-Joe

[Donald]

m3nth,

“When the [Disconnect type definitions and remove unused polymorphic VI instance] box is not checked, the VI will compile.”

Just file this away in case you still get Error 1003 after your Excel ActiveX woes are resolved:
Do you have any strict typedefs in the problem VI? Would disconnecting them (without any programming adjustments) create errors in the block diagram?
The problem has come up a few times in this forum and others, a good example discussion being over on the LAVA forums here.

[m3nth]

Real good info. Thanks.

[GregD]

New Twist on this Error:

I developed an equivalent to the Active-X Report Gen Toolkit for an excel App in LV 5.1 (before it came available), and have upgraded it succesfully through LV7.0 using app builder and with different version of excel (97 and 2k), and win2000. However, it appears there is a conflict now with LV7.1 I have a new fresh PC with the Nov '04 version of LV7.1 and office 2000, on WinXP. When compiling, error 1003 appears. I have isolated the problem to the presence my Active-X vi and the RGT. The issue is that I use both methods for report generation and they conflict somehow. When I try to build a stand-alone Test-VI with my Active-X excel report generator subvi, it works fine. When I add the _Excel Dynamic VIs.vi as a dynamic vi to the build process (even though I'm not using any of these VIs) I get the 1003-error, with and without the "check box" for polymorphics set. The Win2000/XP change may be another possibility. The "force compile" of my main VI does not return a "broken arrow" and the code runs fine in the development environment.

I am currently trying to isolate which _Excel Dynamic VI is the culprit.

[GregD]

Error 1003 error possibility

Found that I had borrowed an example vi and had been carrying it along outside of the Program Files\Nat'l Instr file structure for several versions. "Row column to Range Format.vi" was a vi I was using and is also the name of a VI in the _Excel Dynamic VI bundle, hence a conflict. Changed the name, all is well

[m3nth]

I would say the debugging problem though, or at the root of it anyway, is that the Error 1003 message doesn't really help you pinpoint problems you're having very easily.

[snyapathi]

Hello GregD!

Thank you for the post. It was useful for me. My case was similar. I have borrowed one VI for recursively finding list of all files in a directory and all its subdirectories. I have edited this VI but kept the same name. The original VI I have placed in User.lib in NI directory structure. When I tried to build executable I go this error. Renaming the edited file has solved the problem. Kudos

Sreedhar