It's hard to tell, but judging by the limited information here and what's in the call stack, this looks like it might be a bug in the grid. But, I also noticed that you are using v7.3 of the grid, which is almost 3 years old. No more updates are being made to that version.
So the first thing I would recommend is that you make sure you have the latest service release:
How to get the latest service release - Infragistics Community
If that does not help, then I'd suggest that you download a trial version of the latest release of NetAdvantage and see if the problem goes away.
If none of that helps, then we would need to have a small sample project demonstrating the error so we could debug it and figure out what it is about your layout that is causing it to fail.
Hi,
I'd certainly be happy to try to find a workaround for you. But there's not much I can do without being able to see and debug the issue. As I said above, we would need a small sample project demonstrating the exception. Are you able to reproduce the exception reliably in a small sample? If so, just post it here and I will check it out.
I'm afraid you lost me with all that stuff about Delphi and tlb's. I don't think our assemblies are any different than any other assemblies in this regard, so if other assemblies work, I can't see why ours would not. If this is a limitation, it probably has nothing to do with the assemblies themselves, it's probably a limitation of Delphi. You might want to ask someone as Oracle if they have had experience with third-party assemblies in situations like this.
As for determining if the latest version fixes the problem, the easiest thing for you to do would be to download a trial version and test it out. You could make a copy of your project, update the copy to the new version, and see what happens.
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.