Hi Aashish!
Good news, figured out the problem...I WAS writing a null to the database (by accident), and while access doesn't mind them - the toolkit is based on SQL standard which i believe does. The program had a cluster that was being initialized, and fed into a loop where it waited for user action. (So we didn't have left over garbage in each field whenever the app ran.) Once the user input all their data, that same wire was fed into the input to populate the array. I thought it would update the cluster as the controls were changed, but I guess the only way to change elements is to unbundle, change and rebundle. (At least thats how it behaves)
Appreciate the help, but while on the topic maybe you can give me a pointer, the only way I could work it so a fresh copy of the data was sent into the cluster, was to make a local variable of the cluster and wire that to the input (See picture). Rather than get yelled at later if I need more help, any idea how to reduce that local so we don't require a duplicate copy of the data? (avoid race conditions, etc.) Or would you even? Guess it boils down to, is there another way to update the cluster in there? I can unbundle, and rebundle, but I'm not sure what I'd do between the two to update all those to feed into the database...its a bit confusing to describe but I think it gets the idea across lol.
I was thinking about a way to do it...and thought maybe I need an indicator for each control, then when the indicator changes, feed that into the control cluster to update from intial and go from there...but thats a copy of data the same size as the local would make, I'd think.
LV7.1, LV8.5, LV2014/15/16