I received the following error when navigating away from an instance of the DevEx XtraGrid (bound to a BO via a BBS):

">

I have tried updating the framework (1.6.6 released version), then I tried updating to the most recent DevEx version (8.2.4).  I have removed the grid and replaced it with another instance.  All attempts have resulted in the same behavior.

Does anyone have any idea why the XtraGrid is causing this error to popup?  Btw, I can answer 'No' and continue using the form.  I'd really like to use the XtraGrid rather than the EnhancedList (which is nice, but lacks a couple of necessary features). 

Thanks for your help!
Bill

Using a DataGridView . . . success.

Using a DevEx GridControl . . . failure. 

The same error popup on window close: "Exception has been thrown by the target of an invocation. Do you want to correct the value?  Yes.  No."  If I select "Yes" the window stays open.  If I select "No" the window closes.

The version of the DevEx GridControl is 8.2.4.  I am running on the latest SF release 1.6.6.  I will try to put this into the support and forums of DevEx.  Maybe someone there can provide some further direction.

You can put this on the DevEx support forum, but it won't help you any.  This has nothing to do with the grid other than the fact that the field is being evaluated on a Dispose.

I know that you don't get what I am telling you, and Greg has tried to tell you the very same thing that I have been trying to tell you.

So let's start over.  You have asked for help, you created a sample that reproduced the problem.  I downloaded the sample that you gave and reproduced the problem on the version 8.1 grid.  I showed you an example of how to resolve the error by trying to make you understand that if you are going to create a custom property that relies on an underlying column pulled back from a query...that column must exist in the result set!!! 

For example, you can't create a custom property that attempts to pull from the CurrentRow if that column isn't within the CurrentDataTable.

You are welcome to post another sample if your first sample did not accurately depict your problem, which at this point it apparently did not since I corrected it and reposted it and you are still not pleased with the results.

If you do not supply "surgical precision-type" help, then you need to supply "surgical precision-type" details, otherwise we cannot help.

We have tried for a week now to help you with this problem and have gotten nowhere other than some frustrated and caustic remarks.  So let's take the emotion out of the equation and start over....by starting with a sample that accurately depicts your problem.  Past that, the bantering back and forth has not gotten anywhere and we are a week into the problem with no resolution....though I and Greg both seem to understand your problem, we cannot seem to make you understand the underlying issue.  So at this point, let's go back to the sample, create one that shows exactly what you are trying to do since you did not like my previous answer, I will correct it and repost it.

Thanks.

You have misinterpreted what I have been writing.  I am not at all intending to be caustic in my remarks.  There is no professionalism in that.  I am extremely grateful for every snippet of help given.  As I implement the ideas supplied here and attempt to fix my problem, I only report back to the forum what is happening.  If I do not follow a certain logic, I mention it.  Not trying to be a dork here.  Perhaps it looks that way.  Sorry.

No worries, we are good, I just want to help you get your problem resolved...and I am sure that you have no issue with that goal either

So that is why I was suggesting going at another sample that more accurately represents your problem so that we can hopefully get to the bottom of this.