SetCurrentCellAddressCore exception - by viperjason

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


11
1
Sign in
to vote
ID 259512 Comments
Status Closed Workarounds
Type Bug Repros 15
Opened 2/21/2007 5:28:46 PM
Access Restriction Public

Description

"Operation is not valid because it results in a reentrant call to the SetCurrentCellAddressCore function."
this occurs when changing a textbox to a combobox on cellEnter.  It only happens when columnIndex and RowIndex are the same.
Sign in to post a comment.
Posted by Boris Shvets on 3/10/2011 at 6:56 AM
I have stumbled upon this issue though double click event on an editable datagridview.
My solution was to make the first column not editable (or one might use a checkbox culomn).
This was the only solution that worked for me.
Posted by RobinBr on 5/18/2010 at 11:57 AM
Found the workaround here: http://social.msdn.microsoft.com/Forums/en-US/winforms/thread/6f6ff25d-bdef-496e-9931-2abd03252ae8
Posted by RobinBr on 5/18/2010 at 11:25 AM
Please post the workaround again!!!
Posted by BvDorp on 11/20/2009 at 7:08 AM
Workaround isn't available anymore. Can it be posted over here?
Posted by Saurabh [MSFT] on 4/8/2007 at 10:14 PM
Thanks for your feedback on the .NET Framework!
Customer feedback is a critical part of a successful, impactful product release. Unfortunately another part is the reality of schedules and the need to get the bits into production. The bug you entered has been reproduced, but our evaluation determined that it does not meet the criteria to be addressed in this release. This evaluation is carefully done and considers many aspects including fix cost, breaking changes, globalization, performance, etc.

Many customers have found it useful to discuss issues like this in the forums (http://forums.microsoft.com/msdn/default.aspx?siteid=1) where Microsoft and other members of the community can suggest workarounds.

Before we even begin work on the next release of the NET Framework release where we can make changes like this one we will devote time to addressing the top issues/suggestion (in terms of number of votes, lack of workarounds, etc). So please do continue to vote for this item if it is causing issues.

Please keep the feedback comming.
Thanks,

UIFx Team