T
teddysnips
Visual Studio 2005
I have a moderately complicated form. It has four User Controls, which
are (somewhat simplified):
1. A tree control showing an employee hierarchy
Below a tab strip with three tabs:
1. A User Control containing a check box (AutoPostback = True), a
couple of labels and a grid (which is itself a user control, being a
handy wrapper for the standard Grid)
2. A User control containing a check box (AutoPostback = True), a
couple of labels, A COMBO BOX CALLED GOOD (AutoPostback = True), and a
grid.
2. A User control containing a check box (AutoPostback = True), a
couple of labels, A COMBO BOX CALLED BAD (AutoPostback = True), and a
grid.
So, I'm testing this baby and it looks spiffy. However, when I dropped
down the BAD combo box (thus causing the first PostBack) the
application barfed with "500: The server can't fulfill your request"
When I investigated further I found that ALL the other controls caused
the same error.
Except.
The GOOD combo box didn't barf - it did it postback as required.
What's really weird is that It then seemed to "enable" the rest of the
form so that all the other, previously barfing controls, now work
correctly. In other words, if I do this:
Load Form
Drop-down BAD combo
Result: 500: The server can't fulfill your request
However, if I do this:
Load Form
Drop-down GOOD combo
Drop-down BAD combo
Result: Happy user.
Anyone any thoughts?
Edward
Anyone got any ideas?
I have a moderately complicated form. It has four User Controls, which
are (somewhat simplified):
1. A tree control showing an employee hierarchy
Below a tab strip with three tabs:
1. A User Control containing a check box (AutoPostback = True), a
couple of labels and a grid (which is itself a user control, being a
handy wrapper for the standard Grid)
2. A User control containing a check box (AutoPostback = True), a
couple of labels, A COMBO BOX CALLED GOOD (AutoPostback = True), and a
grid.
2. A User control containing a check box (AutoPostback = True), a
couple of labels, A COMBO BOX CALLED BAD (AutoPostback = True), and a
grid.
So, I'm testing this baby and it looks spiffy. However, when I dropped
down the BAD combo box (thus causing the first PostBack) the
application barfed with "500: The server can't fulfill your request"
When I investigated further I found that ALL the other controls caused
the same error.
Except.
The GOOD combo box didn't barf - it did it postback as required.
What's really weird is that It then seemed to "enable" the rest of the
form so that all the other, previously barfing controls, now work
correctly. In other words, if I do this:
Load Form
Drop-down BAD combo
Result: 500: The server can't fulfill your request
However, if I do this:
Load Form
Drop-down GOOD combo
Drop-down BAD combo
Result: Happy user.
Anyone any thoughts?
Edward
Anyone got any ideas?