Peter,
I for one maintain a variable (tab / return) that duplicates the content of the table field, and every user action first targets that variable and then I refresh the table (put myVar in fld myTable). This is the safest & quickest way I've found to bypass all possible problems that can arise from the "unfinished" table field in the few last Rev versions. It runs pretty quick, even for "large" tables (for instance : 500 rows & 40 cols). I haven't tried with "huge" data structures... JB > Hi Frank > > Thanks for the response. Unfortunately your recommendations only > work for ordinary fields not table ones. The problem is that when > you start editing into cells, the field text property is clearly NOT > being used to hold the edited cells. From other messages on the list > it seems that hidden data structures are used for this. > > This is why I'm after some documentation - how to I get at the hidden > data structure to read/write/empty under script control? > _______________________________________________ use-revolution mailing list [email protected] http://lists.runrev.com/mailman/listinfo/use-revolution
