Create 64-bit compatible versions of MSComCtl and MSComCt2 controls
We have been advised to consider upgrading to the 64-bit version of Office throughout our company. As a world leading financial institution we have a lot of users that use Excel applications that require large amount of memory and processing power.
We have a dedicated VBA development team that make extensive use of the controls and we need 64-bit versions of the controls before the roll-out can go ahead as a large number of critical applications will no longer work in 64-bit Excel.
Nick Sutton
shared this idea
27 comments
-
Aurélien
commented
I use the mscomctl.ocx and I really need that it will be always working and even improved.
Thank yo
-
Roland Miller
commented
I use the mscomctl.ocx and I really need that it will be always working and even improved.
Thank you.
-
AUPETIT Dominique
commented
Hello has all,
I have Windows 7 in 64 bit, then the professional Office Pack 2013 well on installed(settled) in 64 bit.
On Excel I make form but on the other hand I have no Listview.
You can advise(recommend) me for the version 64 bit
Thank you again,
Dominique -
TPN
commented
VBA is entrenched and wont go away any time soon. Microsoft knows this and its a conundrum for them. Most Excel users, and most VBA scripters that are Excel savvy, will never understand VSTO and dot net. I cant see my assistant learning C# or whatever pejorative they're calling VB these days, "visual fred" or whatnot. But he can whip out some of the most amazing VBA I've seen, integrate Excel and Access with Outlook and so forth. In short, VBA isnt going away. They'll lose a significant number of advanced Excel users who rely on it.
-
Anonymous
commented
I highly doubt that Microsoft will ever create 64 bit versions of those ActiveX controls. Read more here https://msdn.microsoft.com/en-us/library/office/ee691831(v=office.14).aspx#odc_office2010_Compatibility32bit64bit_ActiveXControlCOMAddinCompatibility
If you want to have both 32 bit and 64 bit support for your app consider switching to using .NET for your app development. VBA is a legacy language(it's nearly identical to VB6 which is long obsolete) and should not be used for development of any serious apps. You would do much better using .NET via COM Interop to interact with the Excel object model for Excel Windows Desktop Development. Check out AddInExpress, VSTO, and Excel DNA. I highly recommend AddInExpress, you can create an app that runs on any Excel Version with any architecture (64 or 32 bit) all from a single code base. Excel also has a Java Script api that can do cross platform addins for Excel but it is not as powerful for Windows desktop development.
-
Kentetsu
commented
I have many applications built under Excel 2010 which, after upgrading to Office 2013 experience non-functioning controls. The main trouble is the loss of the DateTime Picker. Would really love to see these controls carried on to the new versions.
-
Daniel
commented
a built in calendar control would be great.