We are trying to migrate an Access application to .Net. To do this we use Microsoft's interop toolkit which allows us to create ActiveX controls in .Net. So what it basically comes down to is this: we create a new interop user control, place some WinForms controls on it, build and register the assembly and use it in Access.
After some extensive tests we noticed that Telerik's WinForm controls do not behave well in an Access environment. In a .Net application the controls work just fine.
Here's some examples of things we've seen:
- RadGridView: crashes when leaving cells with a RadSpinEditor as their editing control. The application shuts down without showing an error. The event log mentions exception 0xc0000fd, which appears to be a stack overflow.
- RadGridView: columns using RadSpinEditor cannot be edited.
- RadContextMenu: navigating through the menu using the arrow keys scrolls 3 items up or down instead of one.
I know the controls are not exactly intended to be used like this, but is there anyone else who had similar experiences with the WinForms controls? And has a solution to make the controls more stable?