WHile I agree its odd because it only happens on some machines, I am not surprised. Small differences (e.g. speed/memory) can really make a difference in uncovering sync issues sometimes with databinding. WinForms in particular have some real black-magic to make databinding work as often as it does. I've been hired to dig into these sorts of problems before and they are usually when databinding situations that are edge cases that maybe the WinForms developers didn't think about or an actual bug.
Thanks, Shawn Wildermuth http://adoguy.com C# MVP, MCSD.NET, Author and Speaker -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Bob Provencher Sent: Monday, June 19, 2006 7:01 PM To: [email protected] Subject: Re: [ADVANCED-DOTNET] Bug with adding datarow to table That sounds possible, but it's odd that it only happens on some of the machines it is run on. -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Shawn Wildermuth Sent: Monday, June 19, 2006 6:56 PM To: [email protected] Subject: Re: [ADVANCED-DOTNET] Bug with adding datarow to table There is a common bug in ADO.NET 2.0 where you create a DataView and don't use the BeginEdit/EndEdit (or whatever the API is called) so the DataView throws an exception about an invalid index or something. So I am drawing at straws until I see a stacktrace...that might point at the real underlying problem (again, most likely a data binding issue). =================================== This list is hosted by DevelopMentor. http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
