Hello,
Let see an example :
1. Assume, you have a grid where we can see all money operations for a person (100 lines) and at the last column its current balance.
2. Assume, you just commit an update on line 5 :
update TOperations set amount = 777 where (IDOperation = 23000)
At this point, the server will commit this without problem as the transaction is fast !
And you want to see, not only the refreshed record at line 5, but all records after, affected the current balance.
3. So, obviously you will say : Ok, i will Re-Open the Query and show the new balance colum.
Humm....the problem is here !
4. In web development, we have to think differently : assume you have a mini server, with low ressources and 500 opened sessions in real time.
The 500 users are doing updates, with re-open (refreshing).
Not tested, but obviouly, our mini server will make a face 🥶
5. Here is where comes "Client Calculation" :
After updating line 5, we don'nt have to re-open the query (saturate the server), but work only on the grid locally, client side
Ovoid technic .Edit .Post as it is server side.
6. Working on the grid locally, client side take advantage of javascript already integrated on known browsers as Chrome, Opera, FireFox, etc...
7. JavaScript on client side (Client Calculation) allows you to refresh the 95 lines in a flash time, without the need to re-call the server, nor even updating anything on sever.
8. I think FmSoft team is doing her best to release a next build with this feature.
😊