Is it possible to develop an Excel-VBA application for i.e. version 2012, but using version 365?
Reason for this question is that I sometimes develop clean VBA applications for clients in 365, but when executing in their environment the code breaks for countless errors, mostly not finding certain command names. Currently, I find myself developing the VBA applications for older versions on the clients' computers as a workaround.
Related
I have developed a VSTO add-in for Excel and created a setup file to install.
Its working fine in office 365/win10, but I want to check how it performs in different office versions such as 2016, 2019 or 365.
How can i do that ? Is there a smarter way to do it within Visual studio or do i need to create virtual pc for each environment and test them one by one.
You can create a VM and test your MSI there for each supported platform/OS/Excel version. There is no smarter way for that.
I Have an add-in that is working on Excel in chrome, excel in Edge, but doesn't work in excel desktop.
Any clues?
Thanks
In the article amitklein gave, it says:
Office will still use the EdgeHTML base for add-ins until a build of Office 365 that supports Chromium is installed on the computer. We expect these builds to ship in 2020. They will likely appear in the Insiders channel in the first half of the year.
I haven't found the Chromium based Office 365 in insider channel so I think the version for now is still EdgeHTML based and Excel uses Edge Legacy.
With the introduction of Excel on Android and iOS, I'm not sure what's the correct method of creating a UDF (User Defined Function) that will work across all versions of the Office 365?
I want my UDF to work on iPad, Android as well as Desktop. What's the official Microsoft way of supporting all of these versions of Office for UDF's?
There is no way to support all these platforms. It will work on the Desktop editon of Office.
I am supporting a legacy application that was written in Access 2003 using VBA. We are updating our systems to Office 2010, with the exception of Access, which will remain the 2003 version. (This is due to several factors pertaining to other groups in my organization.)
We use Access as a front end for running reports out of MS SQL and Sybase databases. Some of these reports open in Excel. During testing, running reports that write to an Excel workbook causes the Access application to crash and exit without a warning message - the application simply disappears from the screen.
I'm not sure what the cause of this is or where I should start looking for answers. Has anybody dealt with a similar situation?
I saved and recompiled the application on the development machine that had Office 2010 installed, and thereafter the application worked correctly with Office 2010 (of course, it no longer works on machines only having Office 2003.) This was, of course, after checking the references were correct. Without any intervention, the reference to Office was for 2010.
After testing with early versus late binding, it would appear the best answer to this issue is to use late binding.
Make sure you are writing to Excel in Excel compatibility mode (.xls).
I've been working intermittently on an Excel spreadsheet for a customer that does some pretty intense calculations. We implemented a security procedure using VBA... At first the requirements were relatively simple, and the overall lack of security in a spreadsheet was discussed and well understood.
Since then the customer has decided that he would like to have the sheet a bit more secure. Under normal circumstances I would simply disable the developer menu via code. Unfortunately I just recently found out that the customer, and many of his customers, are using Mac Office. (There are some customers that are even using 2008 and they found out the hard way that 2008 stopped supporting VBA)
My question is; is it possible to disable access to the Visual Basic editor in Mac Office in versions Pre 2008, and versions 2011 and after since from the research I've done so far points to a return of VBA support in Mac Office in 2011.
Unfortunately I do not have access to a Mac Office version to even really look through the application and or/test different solutions. In Windows it is possible to right click the VBA project and choose protection from the VBAProject Properties and choose "Lock project for viewing". Does this option exist and is it effective in Mac Office?
Any help/suggestions would be greatly appreciated.
I'm pretty sure you can lock projects in Mac Office the same way you can in Windows. Keep in mind that a project that has been locked in one version of Excel cannot be unlocked with a different version. So, if your customer needs to be able to unlock, they will need to use the same version of Excel you used to lock it.