How about using one method to remove the handlers and another to add. Then you're swichting them on and off in just two places. i.e. private void RemoveHandlers() { button1.Click -= new EventHandler(clickHandler); ---- } private void AddHandlers() { button1.Click += new EventHandler(clickHandler); ---- }

Thanks for the response. What I ended up getting working was looping through the items list (which will never be more than a dozen or so), rather than the List<> of items that needed to select. From that, I could parse the correct object from the associated datarow (by casting it as such) and then compare that to the list of approved items. uxlbSuite.SelectedItems.Clear(); List objectsToAdd = new List(); foreach (object unit in uxlbSuite.Items) { System.Data.DataRowView Row = unit as System.Data.DataRowView; if (Row != null && toSelect.Contains(Row["ID"].ToString())) { objectsToAdd.Add(unit); } } foreach (object unit in objectsToAdd) { uxlbSuite.SelectedItems.Add(unit); }

prior to the form being shown, these two are called in this order, assume everything not declared is declared before. public void LoadForm() { PlayerSource = new BindingSource(); //assign to prepopulated table PlayerSource.DataSource = myClient.PlayerList; TeamSource = new TeamSource(); //same deal TeamSource.DataSource = myClient.TeamList; //assigning of Player info to labels through databinding //databind player combobox uxcbPlayer.ValueMember = "PlayerID"; uxcbPlayer.DisplayMember = "PlayerFullName"; uxcbPlayer.DataSource = PlayerSource; //databind team combobox uxcbTeam.ValueMember = "TeamID"; uxcbTeam.DisplayMember = "TeamFullName"; uxcbTeam.DataSource = TeamSource; } public void LoadData() { CurrentPlayerSource = new BindingSource(); CurrentPlayerSource.DataSource = myClient.CurrentPlayer; uxcbTeam.DataBindings.Add("SelectedValue", TeamSource, "Team", false, DataSourceUpdateMode.OnValidation, ""); uxcbPlayer.DataBindings.Add("SelectedValue", TeamSource, "PlayerName", false, DataSourceUpdateMode.OnValidation, ""); } In the Team.SelectedValueChanged event I call this funciton: public void FilterTeam () { if (uxcbTeam.SelectedValue != null) { if (PlayerSource != null) { PlayerSource.Filter = "Team = '" + uxcbTeam.Text + "'"; //uxcbBuilding.SelectedIndex = -1; //reset cbBuilding Selected Index } } } Upon needing to save, I call CurrentPlayerSource.EndEdit(), and then deal with the data. The problem is that upon .EndEdit, the new value of the Player dropdown is not committed back to the database. Say if team A and Player A2 are selected initially, and the team is changed to team C, players C1-Cwhatever populate the second dropdown, C1 is shown initially, but on EndEdit, A2's value is put back in the datatable. If the user opens the player dropdown, and then selected the programatically-selected C1, then upon .EndEdit(), C1 is sent back, but I'm looking for a way to somehow "catch" the change on the second set and have the databindingsource (in this case, CurrentPlayerSource) catch the change.

Worked perfectly, thanks.

Yeah, he's a good author. Programming C# 4th edition got a bad review in the last CVu magazine by these guys - ACCU[^] I've not seen the 4th ed but I own the first ed and thought it was excellent. I did take issue with the critic though. Kevin

Hello If you have .Nt 2.0 you can handle PreviewKeyDown event which can catch the tab key, or handle the CellEnter event and shift the focus to the nearest non-readonly cell. Regards:rose:

No, the session variables never leave the server. If you want to set a session variable from the client, you have to send the information to the server and do the change on the server. --- b { font-weight: normal; }

Select Field1,Field2,Field3 From TableName Where Field1 In(Select Field4 From Table2 Where Field4 Like '%Something%')

Figured out my issue. Since I had a number of stored procedures and functions, I needed to perform a massive drop and add (drop sp, drop fun, drop assem, add assem, add fun, add sp), but that appears to have successfully transfered them over. The msdn link above is really helpful for generating those files, but I think they probably need to include a paragraph or so about dealing with dependencies.

That was exactly what I was looking for. I completely zoned out and forgot to check MSDN, but this link has more than what I was looking for. Thanks

That did it, thanks.

Thanks, you helped me find my issue. All of my various usercontrols inhereted a definition for a .Save() method that would call endedit, but in one of them I set flags to mark a "last modified date" field, that was giving me false positives if I was just trying to check. EndEdit() was the end solution though. Thanks.

Found it, I needed to change the second line above to include .Select().

Turns out all I needed to do was re-open the designer where I was trying to use the custom form. That got it showing up. Anyways, thanks for the help, and the advice on [Description()]

Drew McGhie wrote: Is there a better way to do this, or am I doing it correctly? Other than the extra closing bracket it looks okay to me. If you need to optimising it then look at the query plan in Query Analyzer because it never ceases to amaze me what SQL Server thinks is optimal in a given situation - I've also had one change somewhere in the database cause an existing query to start running a lot slower than before. I feel that database optimisation is an on-going process rather than something you do once when you are doing your initial development. Anyway, an alternative to your code: SELECT TOP 1 Locked, TKey FROM Table WHERE Type IN (0,1) AND PKey = @Pkey ORDER BY TKey DESC "On two occasions, I have been asked [by members of Parliament], 'Pray, Mr. Babbage, if you put into the machine wrong figures, will the right answers come out?' I am not able to rightly apprehend the kind of confusion of ideas that could provoke such a question." --Charles Babbage (1791-1871) My: Website | Blog

The difference in performance is so very small that it's more a matter of taste and style. The second code is a bit more efficient, mainly because it doesn't contain a jump. If you only run the code a hundred times though, the difference in execution time is so small that it's not even possible to measure. --- b { font-weight: normal; }