how to avoid getting the same data continuously

[altenbach]

If you want each client on it's own row, you do waht you currently do. If you want to store historical data for each client, you need more rows. The two requirements don't seem to be easily compatible. How do you want the table to look like after each client has sent 5 sets of data, for example.

[RavensFan]

If you want data to persist between loop iterations, then you need to use a shift register like Altenbach said in message #2, then you build the new data onto the bottom of the array in the shift register.

I would recommend looking at the online LabVIEW tutorials
LabVIEW Introduction Course - Three Hours
LabVIEW Introduction Course - Six Hours

[achfire]

yes i want to store historical data for each client.for example i will have 5 computers in where i will install 5 clients;when a user is the 1st client when he enters all his data i want them to be stocked in a table;but when he goes and a new user comes and uses the same computer(the same client) and enters his data i want to get them in the same table,and the same thing for all clients

[achfire]

is this what you were talking about Mr RavensFan

[RavensFan]

No.  You are just putting the same empty array back into the shift register.

You need to maintain the array in the shift register, add new data at the end, and put that back into the shift register.  You'll have to move your header part of the array to outside the loop.

You really need to learn how to use the debugging tools such as probes and highlight execution so you can figure this out yourself.

[altenbach]

---

@achfire wrote:

is this what you were talking about Mr @RavensFan

---

Nooooo! Think!!!

Your shift register has no purpose because all it ever contains is an empty array, forever. It start with an empty array, and that same empty array if fed back into it on the right side. The shift register needs to be a 2D array (wired to the table indicator), and you need to append a new row each time. This is very basic LabVIEW, and you are not there yet. Try to figure it out with logic.

[achfire]

thanks a lot for your precious help;i'll use what you told me.i hope that it will solve the problem once and for all this time

[achfire]

thanks a lot for your help,i figured a way to solve the problem by using feedback node,and i replaced datasocket with shared variable

[altenbach]

---

@achfire wrote:

thanks a lot for your help,i figured a way to solve the problem by using feedback node,and i replaced datasocket with shared variable

---

I am sure you did more than that. 😮

Feel free to post your final code for review and comments.

[achfire]

with pleasure,if you notice anything that can be changed to improve th pg i'll do it