cancelar
Mostrando los resultados de 
Buscar en lugar de 
Quiere decir: 

Example Shock Absorber Performance Report not working correctly

¡Resuelto!
Ir a solución

Hi,

 

I have a problem in using the "word edit cell.vi" to manipulate multiple cells in a table of a word document. What this vi is doing on my system is to insert the values of the first column in all other columns. Check out the example Shock Absorber Performance Report. If i run this report, all values are identical to the first column which I think is not the supposed behaviour of this example.

Do you see the same behaviour or is just on my system?

I'm using LV 2013, Word 2010

 

best regrads

Urs

0 kudos
Mensaje 1 de 8
3.930 Vistas

I did not get what you described.  Below is what I get using LV2012 + Word 2007.

 

 

0 kudos
Mensaje 2 de 8
3.923 Vistas

Thanks for the fast answer.

 

My result is: shock_absorber.PNG

And I get the same Result with LV2011, LV2012 in combination with word 2010.

Does anyone have an idea what could cause such a behaviour and how to fix it?

0 kudos
Mensaje 3 de 8
3.914 Vistas

Did you probe the values from table going to the report?  It could be something with the Simulate Data sub-vi.

 

In the image below, the values from the table are shown in the (large) 2D array inside the red circle.  You should be getting something similar.

 

 

0 kudos
Mensaje 4 de 8
3.907 Vistas

In case the VI was modified...  You should be able to find it inside the attached library..

0 kudos
Mensaje 5 de 8
3.902 Vistas

Nope, table seems to be fine!

Shockabsorber.PNG

Are there any special settings in word which I have to adapt?

 

How is your VI "Word_Update_Table.vi" looking like? Is there a way to somehow force this vi to update two columns?

As far as I understand the word table is somehow updated with this paste invoke node. Do you have any idea of a setting to get more information about where the error is? For example a modified Input or a manual build update table vi?

Unbenannt.PNG

 

 

 

0 kudos
Mensaje 6 de 8
3.865 Vistas
Solución
Aceptado por urssieg

I found the solution thanks to the thread Solution and Thoric's answer.

It seems to be a problem with word 2010.

You will find the same for loops in "Word_update_table.vi"

 

Attached you will find the modified vi.

 

 

 

0 kudos
Mensaje 7 de 8
3.860 Vistas

Thanks for the link to the solution.

 

Don't you just love how MS is able to retain compatibility within its different version of software applications?  😛

0 kudos
Mensaje 8 de 8
3.849 Vistas