I'm sure this is a stupidly simple thing to fix, but I'm feeling a bit stumped at the moment.
I've just created a custom tab in Tessitura using a custom table connected to an InfoMaker object.
The custom tab works in so far as I can delete or add entries to it. However, once an entry is added, if I try to change the data in a field, or delete the data in the field, it will appear to change, but if I move to another tab or click Save, nothing happens and once I come back to the tab, the old bits will be there.
Meanwhile, I can add new values to blank fields with no trouble at all. It's just modifying existing fields that's giving me grief.
Hints, anyone?
Lucky last – thanks for that, Fran! It was the columns out of order on the SELECT statement. I fixed that up and it’s all working fine.
Actually, I spoke too soon. But at least now I know exactly what the problem is.
What I'm having trouble with is saving changes to a custom screen, if I delete the contents of a field.
It's a number field (int to be specific), so to give an example, if I was to change the number from 100 to 99, it'll save no problems. If the field is blank and I add a new number, then that's fine too.
But if I backspace out the 100 and move to another tab, I won't be prompted to save and when I come back to the custom tab the 100 is back.
Has anyone seen this one before? I checked the underlying table to see if it accepts nulls and it does, so I'm not sure why I'm having this issue.
Daft question, but is the number field in question nullable?