I have Excel 2000 but target PC has Excel 2003

[nyc_(is_out_of_here)]

I have Excel 2000 installed on my PC. My client's PC has Excel 2003.

When I use ActiveX to write to Excel files, the VIs end up broken when they are taken over the target PC.

Is there anything I can do to make this work short of installing Excel 2003 on my PC?

[MikeS81]

Hi nyc,
i think the difference between Excel 2000 and 2003, in your specific case, is the change from value to value2. So i recommend to use a dynamic call of your vi´s, one use the "value" property and the other one the "value2".
I think you can upload your vi and someone with labview2003 can save it executable for you.

Mike

Message Edited by MikeS81 on 05-20-2008 09:17 PM

[smercurio_fc]

There are other differences, and us generating the exe for him is not that practical. See here.

[MikeS81]

Hi smercurio,
that is correct, but it is not necessary, because he don´t have to insert this vi´s into the exe. They can be loaded dynamically from outside.

Mike

Message Edited by MikeS81 on 05-20-2008 09:44 PM

[smercurio_fc]

Sorry, must have misunderstood you. I thought your statement "I think you can upload your vi and someone with labview2003 can save it executable for you." implied that we were generating the executable.

Still, it would be beneficial for the OP to take a look at that thread as it contains useful information (and indicates the method of dynamically loading the VIs as a potential solution) and may be of use long-term.


Message Edited by smercurio_fc on 05-20-2008 02:50 PM

[MikeS81]

Hi smercurio,
i mean that someone can change the specified properties to this, used in Excel 2003 and to upload it, not to build the executable.

Mike

Message Edited by MikeS81 on 05-20-2008 09:53 PM

[nyc_(is_out_of_here)]

I should add we are not building an EXE as the version of LabVIEW we have does not come with an Application Builder.

Does that make a difference?

[Karunya_R]

What version of labview are you using? The application not being an executable should not make a difference. For office 2003, it needs to be Value2. Try changing that first.

I would still recommeded that you at the forum that smecurio has recommended.