Hi,
A red X indicates that the something threw an exception during the grid's (or any controls) OnPaint method.
The most common cause of this kind of error is a threading issue. Is your application using multiple threads?
The exception message you listed seems to indicate some kind of math error. So I suppose this could occur if you are using images in your grid and those images are extremely large.
Another possibility is that the exception is being raised by some code in your application and it's not showing up in the right place because it's being caught and handled. This will happen in certain event handlers. So you might want to try setting Visual Studio to break on all run-time exceptions and see if it will take you to a specific line of code.
There's no event that fire when the grid's data binding has completed after InitializeLayout, because DataBinding is never complete, it's an ongoing process. If you can post the call stack from the exception, that might provide more of a clue.
landerson999 said:1) Can you guaranty me that having the next version of infragistics will not leave us crippled seeing as we are using vs2005, and would not like to hear that we need to upgrade to vs2008 or 2010 to use your product.
The assemblies are built against the CLR2 framework, so in theory, they should work in VS2005. I encourage you to download the trial and test them out.
landerson999 said:2) We have full support for our problems pertaining to updates as the last time we updated with Infragistics the version, we ended up with the .resx problem not being resolved for our projects being converted from 2003 to 2005, if you remember any of this...
Hm, I don't really remember a resx issue. Could you provide more details?
Once again, downloading a trial version and testing it out should reveal any major issues with the upgrade.
We try very hard to keep things backward compatible. But there are some things that are unavoidable when there are bugs that have to be fixed and some issues are just impossible to foresee in such a complex environment. As a general rule, though, any change in behavior which was not clearly a bug, is considered a bug and we should fix it.
landerson999 said:3) We will need to find out if we are allowed to distribute the dll we are getting the error i mentioned above to our client, in order for him to use/call our modules...from delphi.
I'm not sure what you are asking here. My understanding is that the license you purchase from Infragistics is a developer license. You can distribute our assemblies to your users for free, as long as their use is limited to run-time. If they are doing any kind of development with the controls, they will require a developer license.
Your questions are more about policy than technical, so I'm probably not the best guy to answer them. You might want to try contacting developer support or sales for licensing questions. :)
I'm still not really clear on exactly what you are doing and exactly what he (whoever he is) is doing.
But I can tell you that if you are writing a UserControl or something like that, anyone who is trying to use that UserControl for development of any kind would have to have a license for the Infragistics controls within it. So maybe this is the same kind of thing.
In such a case, I would expect the exe to raise a licensing exception, though, so that doesn't seem to be the case here.