PC SOFT

FOROS PROFESIONALES
WINDEVWEBDEV y WINDEV Mobile

Inicio → WINDEV 2024 → How to refresh a row in a TableControl with data "loaded in memory" ?
How to refresh a row in a TableControl with data "loaded in memory" ?
Iniciado por b.rohde, 28,jun. 2016 12:42 - 2 respuestas
Publicado el 28,junio 2016 - 12:42
Hi,
I changed a Table control from "direct access to a file" to "loaded in memory".
So my clients can benefit of the direct input to the FILTER CONTAINS-function in the Column-Header.
After adding a record to the file I refresh the TableControl with Tabledisplay...taCurrentFirst.

The TableRow - as described in the documentation - doesn´t refresh, neither the edit-controls, whitch are linked with a key to another file.
How is the trick to refresh the table row and to fire up the code as in the section "Selecting a row..." of the tablecontrol ?

Would be very happy for a suggestion.
Best Regards
Bertrand
Publicado el 28,junio 2016 - 14:41
Hi Bertrand,


Le 6/28/2016 à 4:42 AM, Bertrand Rohde a écrit :
Hi,
I changed a Table control from "direct access to a file" to "loaded in
memory".
So my clients can benefit of the direct input to the FILTER
CONTAINS-function in the Column-Header.
After adding a record to the file I refresh the TableControl with
Tabledisplay...taCurrentFirst.


I do it with tainit, so that everything is reloaded correctly. I'm not
sure it's possible with tacurrentfirst in that case.

But, as the table is loaded in memory, nothing prevents you to modify
the colums content by CODE.

The TableRow - as described in the documentation - doesn´t refresh,
neither the edit-controls, whitch are linked with a key to another file.
How is the trick to refresh the table row and to fire up the code as in
the section "Selecting a row..." of the tablecontrol ?


That last part is easy: do an executeprocess(table,trtselection)

Best regards

--
Fabrice Harari
International WinDev, WebDev and WinDev mobile Consulting

More information on http://www.fabriceharari.com
Publicado el 28,junio 2016 - 15:48
Hi Fabrice,
very helpful !!

executeProcess(...) is the solution.

Some things are behind my horizon ... but sometimes ...
Best regards
Bertrand