I posted an issue on this on the WEB list, but no response, have done some further digging, and have found something peculiar that I would like to have explained.
Briefly, I have an ASP.NET Web datagrid with three button columns and an Edit Command Column. The grid is configured in the aspx page to reference the proper Update, Cancel and Edit procedures in the Code Behind page. When adding a new record, the operation failed, and the trace showed that the code was in the dg_ItemCommand procedure. That procedure used a Select Case structure to differentiate between the handling of the three button columns, but some common code was outside the Select, which is why my update hung. I moved the code back inside the Case statement, and the trace fell through the ItemCommand to the Update Command. My question is what is the logic of having the Update button (and presumably the Cancel and Edit buttons as well) loop through the item comand procedure? I realize that the Update, Edit and Cancel functions are subsets of the Item Command, but I would have assumed that the purpose in referencing specific procedures from the aspx side was intended to shortcut this path. I would appreciate any insights. Thanks Jeff Little CounselTech LLC You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
