Have you ever jumped back to normal view from print preview and noticed the annoying page break lines? They look distracting. They are like a naughty kid shouting for attention. look at me!!!
How do we get rid of those lines after completing our business with print preview?!?
Very simple. We just copy everything, press CTRL+C and then paste in a new workbook!
Of course, I am kidding. There is a better way.
You can click on Office button > Excel Options > Advanced > Scroll down to “Display options for this…” and then un-check Show Page Breaks option.
Aah, it would be much more simple to take a flight, go to Colombia, visit a coffee estate, gather beans, bring them back home, roast and ground them and make a coffee.
But then, we are not after Coffee. We are after those nasty print preview lines.
So here is a much simpler option to get rid of them, on click of button.
We just write a macro.
- Press ALT+F11 in your workbook to go to Visual Basic Editor (VBE).
- Now, locate Personal macros workbook in the project explorer. Just open the macros module (or insert a new one). [more on this here]
- Write a single line macro like this:
Sub disablePageBreaks()
ActiveSheet.DisplayPageBreaks = False
End Sub - Save your personal macros workbook.
- Come back to Excel (ALT+F11 again).
- Add this macro as a button to Quick Access Toolbar
- Now, you can just press the QAT button or use the relevant ALT shortcut (for eg. if the macro button is 4th one in QAT, you can just press ALT+4 to run it).
That is all. Now with all the saved time, you can go to Colombia for a cup of coffee. Make sure you bring me a kilo of that Juan Valdez beans.
More on Printing:
If you like to print and hurt a few trees, make sure you have read these.
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.