LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

error when open microsoft word

I am having a problem when open existing word file. Last time in LV 6.1 working fine. then I switch to LV8, then I cant open. I upgrade to LV8.01 then the problem solve. but somehow it still give me error even in lV 8.01. when I transfer the working VI to another PC with LV8.01, still give me error. I do not know why. please advise.
------------------------------------------------------------------
When you feel sad, laugh
Download All
0 Kudos
Message 1 of 6
(3,087 Views)

since I cannot attach more than 3 files nor cannot zip it.

here is the no error.llb.

 

thanks

with best regds,

Saw

------------------------------------------------------------------
When you feel sad, laugh
0 Kudos
Message 2 of 6
(3,086 Views)
Hello nayisoe,
 
I'd like to help you out, but I'm a little confused here. What is the error you are getting? I see the two screenshots -- one has a broken arrow and the other does not. Is that the problem? It looks as though one of the .llb's you attached does not have an issue, so is it fixed now?
 
It's possible that the change was not the version of LabVIEW, but the version of MS Word. For example, on the broken VI you can re-select the automation reference and then rewire the property & invoke nodes. I noted on the broken on .llb that the invoke node was pointing to the wrong method (likely because the object specified by the automation refnum had changed).
 
I'm sure we can figure this one out!
Charlie S.

Visit ni.com/gettingstarted for step-by-step help in setting up your system
0 Kudos
Message 3 of 6
(3,050 Views)

Hi, the screen shots are taken on the same computer.

 

Sorry I uploaded the whole llb. In fact the vi that contain error is the “open existing file.vi”in that llb and that vi has a problem. Like I posted in my screen shot, one cannot be run with broken arrow however the other one can be run on the same PC (but I noticed that the invoke node input are a bit different from one and another).

 

And when I transfer those vi on another PC (with same version of LV8.01) and it somehow become reverse (problem vi become no problem and no problem vi become problem). Both using office xp and window xp so I do not know what is the error. Like you say may be somehow because of the office version but I don’t get it since both PC use office xp.

 

Thanks and with best regds,

Nayisoe

------------------------------------------------------------------
When you feel sad, laugh
0 Kudos
Message 4 of 6
(3,046 Views)
Hi Nayisoe,
 
This behavior sounds odd to me. I can open the error.llb and run it just find on my computer here (Win XP & Office 2003). However, I do get a broken arrow for the no error.llb. How did these two versions come to be? Were they created on two different computers? If you create one from scratch and try to run it on the other computer does it demonstrate the same behavior? Does it demonstrate it on any other computers (besides these two)? I realize you have the same version of office on both computers -- is it the same service pack for office?
 
Hope this helps narrow it down,
Charlie S.

Visit ni.com/gettingstarted for step-by-step help in setting up your system
0 Kudos
Message 5 of 6
(3,024 Views)
This vi originally is from LV6.1, when I upgraded to LV8.0, the error start to occour. Then when I upgraded to LV8.01 suddenly solved. but somehow I move the vi to another PC and all mess up and become two vi one cant be run and one can run but behave opposite in different PC. I think coz of version changes well in any case, I have a vi that can run is good enough. just hope it wont give me error when I build into .exe 😄
------------------------------------------------------------------
When you feel sad, laugh
0 Kudos
Message 6 of 6
(3,016 Views)