turbodb

We have had some fun splash screens in the past. Of course, these rarely make it out to production versions of Excel :-)

https://onedrive.live.com/?id=592B05F76554281F%2156415&cid=592B05F76554281F

Cheers, Dan [MS XL]

If you ever visit Redmond, you can pick one up in our company store - building 92 :-)

Cheers, Dan [MS XL]

@ViperSRT3g - I'll address your questsions a bit more broadly - how we're approaching extensibility in Excel these days.

We love VBA, and we plan to keep it around for the foreseeable future. As we add new features to Windows Desktop and Mac versions of Excel (where VBA is supported), we’ll continue to add object model for those features (see http://dev.office.com/blogs/VBA-improvements-in-Office-2016), so you have programmable access to all of the capabilities of the application.

That said, the VB runtime was built long before today’s cross platform world (on the VB6 platform which the Visual Studio team has talked about on UserVoice – see http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/3440221-bring-back-classic-visual-basic-an-improved-versi), and with the significant investments we’ve made to run Office across multiple platforms, we want to bring all the great scenarios VBA enabled into this new world and we also want to take advantage of the new opportunities this new world creates for our customers. This has caused us to explore new approaches in order to address the new opportunities of a cloud anchored, cross device world (service connectivity, cross-platform authoring and execution, standards-based languages, cloud based deployment/management, and more).

An early stage of this work is the cross-platform JavaScript APIs available to developers in Office 2016, and we are actively working on dramatically extending that API set to be in line with the existing VBA/COM OM. The good news here is that the new APIs will work regardless of the Excel endpoint/device, which will mean that solutions will be much more universal than they are today. Once we’ve broadened the API set, we’ll start working through some of the tooling (a more modern editor than the VBE) and macro recording.

So, yes! We are in the process of adding other scripting languages to Office and Excel, and we're doing it with cross-platform portability in mind. We're starting with Javascript, and as we get further along that path, we're likely to look at other languages as well.

Cheers, Dan [MS XL]

Just disable the F1 key yo. Open up VBA create an add-in that runs the following code. Load that add-in when you start Excel and badabing, you're set yo.

Sub DisableF1()
Application.OnKey "{F1}", ""
End Sub

-Dan

Do you need the actual 32K in the cell, or would metadata associated with the cell work as well?

-Dan