Defaultbutton inside detailsview- best practise?

[Not Me]

Hi,

I've been trying different ways of getting an insert button within a
detailsview control to be the default button when the return key is pressed.

Using a panel and itemtemplates I get the exception "{"The DefaultButton
of '' must be the ID of a control of type IButtonControl."} - why it
thinks I'm referencing ''? Is it a scope issue because the button is
within the itemtemplate?

an alternative was just sticking with a commandbutton, and
programmatically assigning the forms' default button (via the
masterpage). However this relied on reading the source, getting the
client name (e.g. ctl108) and including that in the code.. surely not an
ideal solution (not sure how arbitrary the control name is, but it's
changed a few times in my testing)

Is there a 'proper' solution I've overlooked?
any tips?

cheers,
Chris

 

[Not Me]

I've been trying different ways of getting an insert button within a
detailsview control to be the default button when the return key is
pressed.

Using a panel and itemtemplates I get the exception "{"The DefaultButton
of '' must be the ID of a control of type IButtonControl."} - why it
thinks I'm referencing ''? Is it a scope issue because the button is
within the itemtemplate?

an alternative was just sticking with a commandbutton, and
programmatically assigning the forms' default button (via the
masterpage). However this relied on reading the source, getting the
client name (e.g. ctl108) and including that in the code.. surely not an
ideal solution (not sure how arbitrary the control name is, but it's
changed a few times in my testing)

For google groups, if noone else

managed a 'fix' by using usesubmitbehavior=false on the buttons I didn't
want to fire when return is pressed. seems ok so far..

cheers,
Chris