Mike Mabey wrote: > On Thu, Aug 21, 2008 at 1:43 PM, Paul McNett <[EMAIL PROTECTED]> wrote: >> >> >> Because a dRadioList always needs to have one of the options selected, >> and you've offered a Value of None which isn't present in the Keys and >> Choices. See my mail in dabo-users. >> >> Paul >> > > Thanks, that explanation helps. So, excuse my ignorance, but how would I > set a default value for the radio list? Better yet, where is Dabo calling > whatever it is that is looking for a radio button matching '1'? IOW, where > is this error coming from that I originally posted: > > Dabo Error Log: Thu Aug 21 14:09:27 2008: No radio button matching '1' was > found.
You must be trying to set radiolist.Value = "1" somewhere. Or, the field in the table that is the source of the data has a value of "1" as the field. And perhaps that is happening before the Choices/Keys have been entered? Are you following my example or your example here? It matters because I don't know what your settings are for Choices, ValueMode, and (if ValueMode=="key") Keys. > Actually I really don't care about a default value, I just want this error > to go away. The only thing I really care about as far as this radio list > goes is I'd like to keep the radio button value when the user creates a new > record, which I'm sure I can figure out how to do. If connected to a DataSource and DataField, the dRadioList will take the Value from the field in the table. So if you want a new record to have the same value as the prior record, then you'll need to override biz.afterSave() to accomplish that. If not connected to a DataField, then the dRadioList should keep the prior value passively. > My biggest concern is that this is the only error I'm getting when the app > runs, yet when it's running and I try to save the new record to the > database, the app says that the changes have been saved, when in reality > nothing has changed in the database and no new record was created. Since > everything else seems to be working fine, this is my only lead as to what > the problem is. This likely isn't the problem. For now, take the dRadioList out of the picture entirely to make sure. > Sorry to shotgun the problem at you, I'm just getting a little frustrated > with this problem. I'm sure there's a good reason for your problems saving. So you do a form.new() and enter values, and then form.save() and nothing is saved? Is a blank new record saved? Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]
