I have an UltraWebGrid bound to a Data Source...
At this point, the entire Grid I created is controlled through choices I have made in the Designer. (Of course, I can do some coding if necessary).
I would like to assign a "DefaultValue" for a particular column so that when a new row is added that column takes on the current DateTime (the column is "DateAdded"...duh...). Inside the Designer the "DefaultValue" is greyed out and i am unable to type anything there. Can someone tell me how to accomplish what I am trying to do? (If I can do it in the designer, that would be nice, if not I can do "code behind". I will be using C#.)
And while I am asking, is there an easy way to enable "CRUD" (Change, Upade, Detele) in the UltraWeb Grid or do I need to add a button for saving? I found the "add" button to add new rows and enabled the grid to allow column cahnges, etc. I just cant get the data to actually save. :)
Thanks for any adivce!Shayne
Yep, I understand (and know that is general forum ettiquite). I just created a new thread because this one ventured off topic. :)
But, we keep using it...lol
shaynejud said:The mystery is why the adds dont "save"... the rows get added visually and I populate the data (with the appropraite data), but when I do the post back the new rows just disappear.
Generally speaking, it's helpful to folks like me if there's one thread per question, and vice versa, so I'll respond over there.
Fair enough and that explains why my Updates and Deletes work without that property set.
The mystery is why the adds dont "save"... the rows get added visually and I populate the data (with the appropraite data), but when I do the post back the new rows just disappear.
OK, now I am more than a little confused. The designer's description of the .BaseTableName property is "The name of the table in the data store." This would make sense to me if you were binding your grid to a multi-table DataSet. But you are binding a single-band grid to a SqlDataSource that returns a single table. When I'm doing that, I never specify a .BaseTableName.
I don't know why your .BaseTableName is being dropped, but it could be because it is not appropriate in that context.
Actaully, I did that first thing this morning, you guys are just usually quicker. :)