How do you get data entered to remain visible after screen change?

[CHRIS_BALSOM]

ABG, I did that and didn't get any notifier message. But the sheet didn't update either. I have attached my AIA for you to look at and tell me where I am going wrong.
RankData.aia (132.6 KB)

[ABG]

Can you post a link to your sheets, so we can see the data?

[CHRIS_BALSOM]

Sure can, Rank Management - Google Sheets

Try this

[ABG]

I see the problem.

The table of cells and components List_Data was initialized at startup, and remained blank ever afterwards, as seen in these Do It shots after loading a couple of those .Text values in the display components.

You were updating your sheet with empty values from the global variables List_Data, with its empty startup data.

What's needed here is a bit of tedium, replacing all those .Text references in List_Data with component blocks (no .anything) and using Any TextBox or Any Label generic blocks to reference the component .Text value at run time.

Since there is no block to tell you if a component is a TextBox or a Label, the app would also need two lists, LabelComponents and TextBoxComponents, filled with the corresponding components, available for IS IN LIST tests to decide which type of Any block to use on the current component.

Things are slow here, so I can start that off for you.

[ABG]

Here's a rework of that table of cell names and text values, where it is turned into a value procedure for immediate reevaluation of all those .Text values on request.

This helps to send all the data to the sheet, but needs extra work if you want to reverse the process and pull back data from the sheet to the Labels and TextBoxes.

The List_Data value procedure needed a little enhancement to serve two functions,

• returning a selected item by number n, or
• returning the total list length, if given an out of range (0) index.

RankData_ABG.aia (133.7 KB)

Proof of update:

Note that I did a bunch of component renaming to facilitate separating out Labels and Textboxes and TimePicker components into separate lists, in anticipation of two way data traffic.

Here's a start on component lists for two way traffic:

[CHRIS_BALSOM]

awesome, Thank you very much. I appreciate the effort you have put in and the breakdown you have supplied in helping me understand. I have to say that I have been a memeber of a number of forums trying to teach myself this and that but your guys here are absolute legends.

I will certainly be tagging you guys in the final effort. @ABG @ChrisWard