Sorry, this entry is only available in Português.
Category: Microsoft Office
Dicas sobre aplicativos Microsoft Office em geral
(Português) Excel – Contar valores únicos em 2025+
Python in Excel, What about it?

In August 2023, we were surprised by the announcement of Python integration in a future Excel update. Wow! This is a big deal, and we need to pay attention to what it means, especially to dispel any misconceptions that may be arising around it.
As a prelude, I must clarify that everything I write here is entirely based on my opinion and public information about the subject, with references at the end of the text.
Python vs. VBA
Every fiber of my being, especially those dedicated to programming, wants Python to be the replacement for VBA. Let me be clear on this point: it’s not. There is nothing, or very little for VBA application programmers in this Python integration with Excel, at least from what has been presented.
So, dear VBA programmer, don’t get too excited. The most that will happen is that you can avoid creating UDFs in VBA by solving everything within a concise Python block in a Excel cell.
Who is Python in Excel for?
It’s essential to make this clear: nobody (except Microsoft and the Office product team) has any idea at the moment who the target audience for this implementation is.
If I had to guess, I would consider two fronts:
- The Office team is targeting the data mining/data science audience, in other words, data analysts. When tools like Excel, the Powers*, Tableau, among others, start struggling with large amounts of data, these professionals often turn to Python. There’s much to unfold here, as it’s not just Python but rather a micro-ecosystem created to serve this audience.
- Since Python is becoming an “almost” universally used programming language, there might be an intention to provide a familiar environment for the market and its users. What makes me a bit skeptical of this theory is that they already tried this with ScriptLab using JavaScript, another widely-used language. Who knows?
But again, for whom is Python in Excel?
I’ve tried to answer this above, as have many other Excel enthusiasts. The fact is, we don’t yet know where this will lead.
Microsoft is an expert at making mistakes, but when they get it right, it’s for real. There are plenty of examples, and Excel itself is one, as it has carried this company for decades.
That’s why it’s too early to predict the acceptance this feature will have. Until about five years ago, Power Query and Power BI were beyond the reach of mere formula writers. Today, they are here to stay.
As an enthusiast, I’m excited. As a programmer, I’m skeptical. As an Excel user, I’m indifferent. As a data analyst, I’m intrigued.
Is Python in Excel for me?
This one’s easy. No. But why?
I am a programmer; I like code. More than that, I like creative freedom. Opening VBA gives me such a great sense of creativity that it’s impossible to compare to the Python prompt within a cell replacing it.
Additionally, Python doesn’t run locally. This is where the success or perhaps the failure of this implementation lies: security, the cancer that has plagued the Office suite for decades that Microsoft wants to get rid of at all costs.
In summary…
It’s early; we can’t conclude much, especially from my perspective as a programmer who likes VBA and has little experience with the Data Science side of Excel.
I am indeed very curious to hear what Power BI colleagues have to say about this. For those of you needing a Python tip, we’re here.
Stay tuned for the next chapters. I have a feeling that Python in Excel is here to stay.
References
StackOverFlow 2023 Survey: https://survey.stackoverflow.co/2023/#section-most-popular-technologies-programming-scripting-and-markup-languages
Python in Excel by Leila Gharani: https://youtu.be/FbBXtqtRnWU?si=f2X3wolD9c0fN-MP
Microsoft Excel just got Python by Fireship: https://youtu.be/8ofsE7xiGho?si=JvyPZ236Oi-O1VF4
Automating Tasks: A Comparison of VBA and PowerShell
When it comes to automating tasks, developers have different options at their disposal. Two popular languages for automation are VBA (Visual Basic for Applications) and PowerShell. While they serve similar purposes, they have different approaches and strengths. In this article, we’ll explore the similarities and differences between VBA and PowerShell, along with code examples in each language.
VBA: Automation within Applications
VBA is widely used within applications like Excel, Word, and Access to automate tasks and extend functionality. It provides a familiar environment for developers who work with Microsoft Office applications. Here’s an example of using VBA to copy files from a source folder to a destination folder based on a search criteria:
Sub CopyFiles()
Dim sourcePath As String
Dim destinationPath As String
Dim fileName As String
Dim file As Variant
' Set the source and destination paths
sourcePath = "C:\SourceFolder"
destinationPath = "C:\DestinationFolder"
' Loop through files in the source folder
fileName = Dir(sourcePath & "\*.txt") ' Search criteria for .txt files
Do While fileName <> ""
' Copy each file to the destination folder
FileCopy sourcePath & "\" & fileName, destinationPath & "\" & fileName
' Get the next file
fileName = Dir()
Loop
' Display a message when done
MsgBox "Files copied successfully!"
End Sub
function to retrieve a list of files in the source folder that match the specified search criteria (in this case, “*.txt” for text files). We then loop through each file and use the FileCopy statement to copy it to the destination folder.
PowerShell: Powerful Command-Line Automation
PowerShell is a command-line scripting language developed by Microsoft, focusing on system administration and automation tasks. It provides a vast range of cmdlets and access to the .NET Framework for powerful automation capabilities. Here’s an example of using PowerShell to copy files from a source folder to a destination folder based on a search criteria:
$sourcePath = "C:\SourceFolder"
$destinationPath = "C:\DestinationFolder"
# Get files that match the search criteria
$files = Get-ChildItem -Path $sourcePath -Filter "*.txt" -Recurse
# Copy files to the destination folder
foreach ($file in $files) {
Copy-Item -Path $file.FullName -Destination $destinationPath
}
# Display a message when done
Write-Host "Files copied successfully!"
In this PowerShell code snippet, we specify the source and destination paths and use the Get-ChildItem cmdlet to retrieve a list of files in the source folder that match the specified search criteria (in this case, “*.txt” for text files). We then loop through each file and use the Copy-Item cmdlet to copy it to the destination folder.
Comparing VBA and PowerShell
Now let’s compare VBA and PowerShell in terms of their strengths and areas of focus:
- Application Integration: VBA excels at automating tasks within Microsoft Office applications. It provides direct access to the object model of the host application, allowing for fine-grained control and manipulation. PowerShell, on the other hand, focuses more on system-level automation and administration, with a broader range of cmdlets for managing operating systems, services, and resources.
- Syntax and Structure: VBA uses a procedural approach, with subroutines and functions, making it well-suited for application-specific tasks. PowerShell follows a command-based approach, using cmdlets and functions to perform operations. It embraces an object-oriented mindset, treating everything as an object with properties and methods.
- Integration and Extensibility: VBA seamlessly integrates with Microsoft Office applications and their object models. It provides easy access to application-specific functionality. PowerShell, on the other hand, offers extensive integration with the .NET Framework and third-party libraries. It supports importing modules and leveraging existing libraries to extend functionality.
- System Administration: PowerShell shines in system administration tasks. It provides powerful cmdlets for managing operating systems, Active Directory, SQL Server, Exchange Server, and more. PowerShell’s scripting capabilities and access to the .NET Framework make it an ideal choice for automating complex system operations and performing administrative tasks.
When it comes to copying files based on search criteria, PowerShell has a clear advantage. Its Get-ChildItem cmdlet provides robust file filtering capabilities, allowing you to search for files based on various criteria such as file extension, name, size, and more. PowerShell’s concise syntax and extensive set of cmdlets make it a powerful tool for efficiently managing and manipulating files.
In conclusion, both VBA and PowerShell are valuable tools for automation, but they have different areas of focus. VBA is ideal for automating tasks within Microsoft Office applications, while PowerShell excels at system administration, command-line automation, and file management. Choose the language that best suits your automation needs and leverage its strengths to streamline your workflows and increase productivity.
