jahuer1 Posted October 23, 2003 Posted October 23, 2003 Masked Edit Control - MSMASK32.OCX ****************************** I have included the MSMASK32.OCX into my toolbox. I put such a Masked Edit on my Form1. When I start the application on my computer where development environment is installed, everything works fine. When I want to start my program on a machine where only the .NET-Framework is installed, it crashes on starting up in the sub "InitializeComponent()" at the following line: CType(Me.AxMaskEdBox1, System.ComponentModel.ISupportInitialize).EndInit() [This is a normal ending instruction for initializing components and is automatically added by the development environment!] I have also put the necessary DLL's for the MaskedEdit are also in the application environment. So, where might be the bug? Quote
Administrators PlausiblyDamp Posted October 23, 2003 Administrators Posted October 23, 2003 The .OCX will need to be installed and registered on the other machine. It's one of the problems using COM components. Quote Posting Guidelines FAQ Post Formatting Intellectuals solve problems; geniuses prevent them. -- Albert Einstein
jahuer1 Posted October 23, 2003 Author Posted October 23, 2003 (edited) Thanks. That's it! - almost. It does work fine now for hardcoded component. But with dynamically created components, there is a claim like: "Your not licensed to use this ActiveX Control" What's about that? ****************************************************** OLD: >I didn't look at it the first time because this ActiveX is in the Windows folder. So at first, you might think its standard and therefore already registered... Edited October 23, 2003 by jahuer1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.