This is going to be a hard one but I am hoping that someone out there has experienced this and can help me.
I have a .Net user control in a DLL. I have embedded this control on to an MS Access Form and it works fine. The Access form thinks it's an ActiveX control, renders it and I can communicate with it. What I have discovered though, is that if my mdb is "Source Control" enabled, somehow this interferes with the ActiveX control rendering - instead I get a message that says "There is no object in this control" when I try to open the form. Again, the same exact form using the same exact DLL with the same exact user control in it works fine in an MDB without source control, but I get that error when it's an mdb with source control. I have tried several experiments and it definitely seems to me like some sort of "interference" from the source control integration. I don't know if this is a problem with ActiveX in general or specifically with the fact that I am using a .Net DLL. If anyone has any ideas whatsoever, I would be extremely eager to hear them. Thanks!!!
I have a .Net user control in a DLL. I have embedded this control on to an MS Access Form and it works fine. The Access form thinks it's an ActiveX control, renders it and I can communicate with it. What I have discovered though, is that if my mdb is "Source Control" enabled, somehow this interferes with the ActiveX control rendering - instead I get a message that says "There is no object in this control" when I try to open the form. Again, the same exact form using the same exact DLL with the same exact user control in it works fine in an MDB without source control, but I get that error when it's an mdb with source control. I have tried several experiments and it definitely seems to me like some sort of "interference" from the source control integration. I don't know if this is a problem with ActiveX in general or specifically with the fact that I am using a .Net DLL. If anyone has any ideas whatsoever, I would be extremely eager to hear them. Thanks!!!
