![vba mscomctl ocx vba mscomctl ocx](https://laser-ne.com/tfqsij/NrDsnTwS49n0Bwa3g8jA5QHaET.jpg)
![vba mscomctl ocx vba mscomctl ocx](https://i0.wp.com/www.ramses.de/WP/wp-content/uploads/faq_access406_41.jpg)
Vba mscomctl ocx windows#
Windows Error Reporting has stopped workingĪnother forum post recommended checking the Windows Event Viewer to obtain log of Error crash report. There are different dialog messages that appear as Excel crashes: I'm working on an Excel VBA application that was working fine under the old laptops, but has now started crashing Excel with the following error:Īn unhandled win32 exception occurred in EXCEL.EXE
![vba mscomctl ocx vba mscomctl ocx](https://i.stack.imgur.com/xsusz.png)
Vba mscomctl ocx windows 10#
Thank you for contacting Microsoft.The client I'm working for recently upgraded all laptops to Microsoft Surface running windows 10 (version 9) and Office 2016: Please don’t hesitate to send us an email and we will be more than happy Kindly check the phone number from the link below Your local Microsoft Customer Service Representative who could activate This information Please be kindly informed that you would have to call Understanding is inaccurate, please let me know. You are having some technical issue with Office 2010. Jaclyn and I would address your Office 2010 inquiry. Have reached Microsoft Customer Service, South East Asia. So I sent them a mail explaining very clearly the problem, and this is the reply I got, concerning activating my product:
![vba mscomctl ocx vba mscomctl ocx](https://www.dbase.com/Knowledgebase/dbulletin/bu13lv01.gif)
And if to wipe out VBA, say it clearly, giving time to port the existing solutions.
Vba mscomctl ocx software#
Summary: In order to continue a reliable software evolution process MS has to port "Common Controls" to 64bit. You might state, VBA is no longer supported and it even does not work anymore. Of course you might say VBA is outdated and will be dismissed, soon. Such a different approach means extra costs, too, which leads to the same conclusion: the developer is f****. A customer simply will not be willing paying for the extraĮfforts - leaving the developer with the costs or forcing a totally different approach. Whether this means creating own controls or switching to VSTO solutions - it is simply not fair. Not supporting "Common Controls" for 64bit will mean a lot of extra work for every serious developer. OK, not 100% fair, but you might have gotten the idea. If I was aware I would have to build the platform myself, too, I could have choosen Open Office to develop on. In my opinion, discussing whether to publish "Common Controls" for 64bit or not, or perhaps a little bit of it but not all, is ridiculous. We chose developing on MS platform because we believed that will give our solutions a long lasting platform to Spend ~3 years developing it - ~3 years they could have spend developing real solutions - real solutions based on your applications. Thinking about the DateTimePicker Ctrl brings me to the point where I am getting concerned - this solution was developed because custom solutions could not be distributed because MS restricted using the relevant control. DateTimePicker Ctrl which has been published as VBA solution using Windows API for MS Access some years ago. ProgressBar, which is just nice to look at but can be substituted by displaying progress within StatusBar and changing Mouse Cursor to Wait (not that nice but works) - or were replaced by pure API solutions thanks Other controls are not that important - i.e. ImageList is required as supporter for both controls. Handy and required - otherwise you would not have included them in your "Common Controls". Controls like TreeView are not possible with pure VBA but Not to mention the possibility to display icons. Ĭommon Controls like ListView excel VBA's Listbox simply by having an included header, ability of being sorted and simplicity of being programmed. Since being labeled "common controls" we expected them being available for ever.