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.

Ok, Mike, here is what is happeneing, I went further with my testing environment, and found these points out. 1) I built a com(tlb) for my vb.net dll, and used vb6.0 to call it. I had no issues, as I believe that vb6 sees the registered dll/tlb from the registry. 2)We have a delphi application that is using the tlb, but was compiled on a machine that does not have infragistic, and then transplanted to the server running the apps and with infragistic installed. My question, is that (not being versed in delphi) Is it possible if the delphi application linked the tlb reference for my dll, it should not have any issues when it comes to using the infragistic...or does infragistic need to be referenced also within the delphi app calling the tlb...this might be the issue, although I am unfamiliar with how infragistic treats application calling their dlls without having any references to them. Also my boss is interested in getting the new version of infragistics, only if we can guarantee this will cure the situation...?

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.

Hi Mike, thanks for the prompt reply, unfortunately, I am not the descision maker, if it were up to me, it would be updated regularly, also we had issues last time we updated from our version to this one (by your suggestion 2 years ago, when we updated from vs2003 to vs2005)
Now we have an issue which is that the grid does not normally do this in any other case, and that if you reload the same form (before GCC comes by) the form loads without a problem, and the error message seems to always mention the gridbaglayout)
If you think this might be related to a bug with the grid, is there any possibility that instead of getting a fix, i could know why the bug is being produced and maybe change the way i coded this(maybe not have any datasource binding before the call to showdialogue?), in order to bypass the need for updating dlls???
I am looking forward to hearing the possibilities for explaining this behavior as I know you guys work really hard to provide quality support, but in this case, we will not be able to update to the next version, and as for 2 years being not nearly enough to suggest there is no more support for a product (hence why xp is still supported today,10 years later) I hope you can find a way to help us with this issue. Thanks in advance