Ever need to extract just the bold portion of some cells automatically? You can use my getBoldText VBA custom function to do that. This function takes a cell and returns the bold portion if any. See these sample results:
Using Custom Functions in Excel
To extract the bold text from cells, we are going to use User Defined Function (UDF) feature of Excel.
This feature let’s us build custom functionality that is not part of Excel.
- Step 1: Go to Visual Basic Editor (Press ALT+F11 or click on Developer Ribbon > Visual Basic)
- Step 2: Right on your workbook in the left-hand panel and insert a new module (refer to below illustration).
Add the getBoldText() Code to your workbook
In the module, copy paste below code.
Function getBoldText(fromthis As Range) As String
Dim i As Integer, size As Integer
Dim output As String
size = fromthis.Characters.Count
If fromthis.Font.FontStyle Like "Bold*" Then
output = fromthis.Value
Else
For i = 1 To size
If fromthis.Characters(i, 1).Font.FontStyle Like "Bold*" Then
output = output & fromthis.Characters(i, 1).Caption
End If
Next i
End If
getBoldText = output
End Function
Save your workbook (as .XLSM file).
Now, you can use =getBoldText() function in your file to extract the bold values from any cell contents.
How to use this function?
Save your workbook (as .XLSM file).
Now, you can use =getBoldText() function in your file to extract the bold values from any cell contents.
The syntax is:
=getBoldText(cell_address)
See this quick demo to understand how to use the function.
How to install this function so it works in all files?
You can also install this function using your personal macros workbook.
Follow below process:
- Click on “Excel Add-ins” button in either Developer Ribbon or Options > Add-ins > Excel Add-ins > Go
- Enable “Personal” macro workbook. This is a macro file that let’s you store reusable macros & custom functions like getBoldText.
- Now go to Visual Basic Editor (ALT+F11) and locate the personal macro file. It would be named personal.xlam
- Expand the file and add a module if necessary.
- Copy paste the VBA code for getBoldText into this module.
- Save and restart Excel.
- Now, you should be able to use the getBoldText across any of your workbooks (on your computer).
Known issues and bugs
In my preliminary testing this function worked fine in Excel 365. I have not tested it in older versions of Excel like 2013 or 2010. If you notice any bugs or issues please report using the comments feature on this page.
More VBA Examples
Check out below VBA / Automation examples to simplify your work:
One Response to “SQL vs. Power Query – The Ultimate Comparison”
Enjoyed your SQL / Power Query podcast (A LOT). I've used SQL a little longer than Chandoo. Power Query not so much.
Today I still use SQL & VBA for my "go to" applications. While I don't pull billions of rows, I do pull millions. I agree with Chandoo about Power Query (PQ) lack of performance. I've tried to benchmark PQ to SQL and I find that a well written SQL will work much faster. Like mentioned in the podcast, my similar conclusion is that SQL is doing the filtering on the server while PQ is pulling data into the local computer and then filtering the data. I've heard about PQ query folding but I still prefer SQL.
My typical excel application will use SQL to pull data from an Enterprise DB. I load data into Structured Tables and/or Excel Power Pivot (especially if there's lot of data).
I like to have a Control Worksheet to enter parameters, display error messages and have user buttons to execute VBA. I use VBA to build/edit parameters used in the SQL. Sometimes I use parameter-based SQL. Sometimes I create a custom SQL String in a hidden worksheet that I then pull into VBA code (these may build a string of comma separated values that's used with a SQL include). Another SQL trick I like to do is tag my data with a YY-MM, YY-QTR, or YY-Week field constructed form a Transaction Date.
In an application, I like to create a dashboard(s) that may contain hyperlinks that allow the end-user to drill into data. Sometimes the hyperlink will point to worksheet and sometimes to a supporting workbook. In some cases, I use a double click VBA Macro that will pull additional data and direct the user to a supplemental worksheet or pivot table.
In recent years I like Dynamic Formulas & Lambda Functions. I find this preferable to pivot tales and slicers. I like to use a Lambda in conjunction with a cube formula to pull data from a power pivot data model. I.E. a Lambda using a cube formula to aggregate Accounting Data by a general ledger account and financial period. Rather than present info in a power pivot table, you can use this combination to easily build financial reports in a format that's familiar to Accounting Professionals.
One thing that PQ does very well is consolidating data from separate files. In the old days this was always a pain.
I've found that using SQL can be very trying (even for someone with experience). It's largely an iterative process. Start simple then use Xlookup (old days Match/Index). Once you get the relationships correct you can then use SQL joins to construct a well behaved SQL statement.
Most professional enterprise systems offer a schema that's very valuable for constructing SQL statements. For any given enterprise system there's often a community of users that will share SQL. I.E. MS Great Plains was a great source (but I haven't used them in years).
Hope this long reply has value - keep up the good work.