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.
Related
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.
I want to submit an add-in only for Excel Online (no Excel for Mac, no Excel for Windows).
Could anyone tell me if it is possible and how to configure the manifest xml file?
The Office store requires that the add-in works for Mac, Windows and Online with optional iPad support. It is not possible to select only some of the required platform. The same code that works on one platform should also work on the other with the addition effort being in the testing area.
I would like to develop Add-in for office Word for Mac (2011 and later). But I cannot find any manuals about Add-Ins development.
Can anybody know how to develop Add-Ins for Office for Mac?
It will be good if anybody suggest me link of Example. I have tried but didn't get any sample.
The good news is that you can use almost all the APIs documented here for MAC as well!
You also want to read this article about how to try your add-ins in MAC or iOS.
Finally make sure you are on the latest possible build! (15,22 as of right now).
Happy coding!!!
The process for building JavaScript add-ins for Mac is pretty much the same as building them for other platforms. There are some specific instructions for debugging on Mac.
However, Office Add-Ins for Mac are only supported starting with Office for Mac 2016 (and even then I believe it needs to be a recent update).
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 have team members that need to be able to checkin VBA modules/classes created in Excel 2007/2010.
I want to be able to use some TFS functionality, ideally from within the VBA IDE.
I don't want to checkin Excel files as artefacts. Ive seen the MSSCCI provider download from MS.
I don't think in this case the Windows shell extensions from the Power Toys helps because I don't want to have to create an additional process for developers to export and/or import class & module files from their work in VBA project maintenance.
Question: Can someone provide a way to use the MSSCCI provider with Excel 2007 (or even Excel 2010 only)? Do you think this would only be possible with custom VBA addin?
Update:
I've thought about using an approach such as making a custom VBA addin and adding some commands that make basic calls to the TFS client object model.
Just found this post from Codeproject from another question this time looking for the same thing but for SVN rather than TFS.
There is a Visual SorceSafe provider for VBE that comes with Office XP Developer. I used it for many years and still have it installed. It does what you want, but using VSS and not TFS.
Note that the product is not supported, but VBA/VBE has not changed since Office 2000. I used the provider for two years for Excel 2003 development with no problems.
I seem to remember recently an article describing how you can use VBA/VSS with the extra benefit of having the code also "posted" to TFS. Since I no longer professionally code in VBA/VSS, I didn't have a need for the article, but did find the topic interesting.
Office XP Developer has a few other tools that make it worth the time to install.
Access Source Code Control and Team Foundation Server
Today's guest writer is Mike Sullivan - a tester on the Access team
With the release of Visual Studio Team System 2008, we've recently received questions from several customers regarding whether or not Team Foundation Server (TFS) can act as a source code control provider for the Access source code control (SCC) component. The answer is yes!
Although many folks refer to Access’ source code control component as “SourceSafe integration,” that only tells part of the story. SCC integration within Access is fully compatible with any provider that implements the Microsoft Source Code Control Interface (MSSCCI). Although Visual SourceSafe is one of the more widely used MSSCCI providers, there are several other products that implement this interface, including Team Foundation Server 2005 & 2008 as well as IBM ClearCase.
However, MSSCCI support in Team Foundation Server is not native and requires an additional add-in available for download:
MSSCCI Add-in for Team Foundation Server 2005 http://www.microsoft.com/downloads/details.aspx?FamilyId=87E1FFBD-A484-4C3A-8776-D560AB1E6198&displaylang=en
MSSCCI Add-in for Team Foundation Server 2008 http://www.microsoft.com/downloads/details.aspx?familyid=faeb7636-644e-451a-90d4-7947217da0e7&displaylang=en
Of course, to enable SCC functionality from within Access, you’ll also need the Source Code Control add-in. This shipped as a free download as a part of the Access Developer Extensions for Access 2007 and as a separate free add-in for Access 2003:
Access 2007 Developer Extensions http://www.microsoft.com/downloads/details.aspx?FamilyId=D96A8358-ECE4-4BEE-A844-F81856DCEB67&displaylang=en
Access 2003 Source Code Control Add-in http://www.microsoft.com/downloads/details.aspx?familyid=2ea45ff4-a916-48c5-8f84-44b91fa774bc&displaylang=en
If you’re interested in taking this configuration for a whirl, you might want to download the Team Foundation Server Virtual PC image that has been made available by the Visual Studio team. Included on this virtual PC are copies of Visual Studio Team System 2008 and Office 2007 Enterprise SP1 (though Access is not installed by default on this image – you’ll need to go to Add/Remove programs within Control panel and launch setup to install Access). This trial image is good through December 31, 2008.
To get the Virtual PC image working, you’ll also need to install the Access Developer Extensions (the MSSCCI add-in is preinstalled). Since VSS is the default MSSCCI provider on the machine, you’ll need to tweak a registry key to get Access to use Team Foundation instead:
Path: HKEY_LOCAL_MACHINE\SOFTWARE\SOURCECODECONTROLPROVIDER
Key: ProviderRegKey
Value: SOFTWARE\Microsoft\Team Foundation Server MSSCCI Provider
Hopefully those of you curious about support for TFS have had your questions answered!