Yes, this is a common problem. The foreign key stored in a field is no longer valid.
Not all legacy applications use declared referential integrity. Sometimes, on some records, foreign keys are broken.
In other languages, how comboboxes deal with this situation is they simply remain blank.
Not with a RadComboBox. Instead, it throws an error.
Now, combine this with an online web application which uses a RadMultiPage and dozens of RadComboBoxes.
How many hours do you have to spend when one of these situations pop up attempting to find which Combobox is the source of the error?
Well, its been 4 thusfar this morning, and I'm no closer to finding which RadComboBox is throwing the error.
Do you think, maybe.... just maybe... you could print the name of the control throwing the error in the error message to aid people in tracking down specifically which control is tossing its cookies? Rather than
Selection out of Range
Parameter Name: value
maybe make it read:
Selection out of Range
Parameter Name: value
Control: Whatever id= name my control has?
?
Not all legacy applications use declared referential integrity. Sometimes, on some records, foreign keys are broken.
In other languages, how comboboxes deal with this situation is they simply remain blank.
Not with a RadComboBox. Instead, it throws an error.
Now, combine this with an online web application which uses a RadMultiPage and dozens of RadComboBoxes.
How many hours do you have to spend when one of these situations pop up attempting to find which Combobox is the source of the error?
Well, its been 4 thusfar this morning, and I'm no closer to finding which RadComboBox is throwing the error.
Do you think, maybe.... just maybe... you could print the name of the control throwing the error in the error message to aid people in tracking down specifically which control is tossing its cookies? Rather than
Selection out of Range
Parameter Name: value
maybe make it read:
Selection out of Range
Parameter Name: value
Control: Whatever id= name my control has?
?