Home

Everyone knows Microsoft Excel is a powerful data manipulation engine, but data lives in databases and only a few Excel experts know how to exploit this natural synergy.

If you are one of tens of thousands of business developers asked each day to:

  • Produce reports from systems such as your ERP, EAM, HRIS, CPFR, CRM, TMS, etc.
  • Write small applications such as Time and Attendance Entry, Help Desk Requests and Time Tracking, PC Inventories, etc.
  • Create data extracts and transformations for system interfaces -

-you can exploit Excel to deliver paperless, interactive, graphical reports in minutes not hours or days and write small applications in hours, not days or weeks. You will exceed your customers’ expectations. You will save your customers time. They will realize benefits sooner.

As developers our value is in the worth of the tools we provide. When our customers get an idea for a tool to help them in their work, the last thing they want is to wait for it. They want it delivered now. They want to be able to use it now. They want it to be flexible. They want it to be graphical. Microsoft Excel is often a great means to meet their ends.

Your customers already have XL so there’s no procurement cycle. They already know XL so there’s no learning curve. They already love XL so there’s no adoption hurdle. All of this is valuable to your customers. What’s left is for you to provide what only developers can – code.

Coding is essential to this process. There are no end user based solutions here other than your final product. Your skills are required. Your skills need to include VBA (the macro language included free in just about all Microsoft applications). If you don’t know VBA, don’t worry. You won’t find it difficult and the examples posted here will make it easy. If you don’t know SQL, don’t admit it. It’s easy. It’s powerful. It’s standard. It’s everywhere. And there are many excellent, free resources on the web. As we go, I will point out resources I use. Perhaps others will share their favorites as well.

If you and your customers own Microsoft Excel (and who doesn’t these days) and your database provider included an ODBC driver (the most prevalent in the market do) then you are good to go. There is absolutely nothing else to buy.

Everyone knows Microsoft Excel is a powerful data manipulation engine, but data lives in databases and only a few Excel experts know how to exploit this natural synergy. Soon – you will be one of them.


Messages

  • Looking into Excel Modeling's Future Carl Stiller posted a simple test in LinkedIn's Financial Modelling’s forum (at right). Reader comments revealed some modelers struggle with the answer. Knowing the answer is critical to ...
    Posted Nov 18, 2020, 6:07 PM by Craig Hatmaker
  • SQL: Getting Worksheet Names SQL can read worksheet names from Excel workbooks even if the workbooks are closed with protected worksheets. NOTE! Power Query may be a better option. The basic method for reading ...
    Posted Nov 3, 2020, 11:21 AM by Craig Hatmaker
  • SQL:Read Closed Workbook by Cell Address SQL can read records from Excel workbooks even if the workbooks are closed with protected worksheets. NOTE! Power Query may be a better option. The basic method for reading from ...
    Posted Nov 3, 2020, 10:40 AM by Craig Hatmaker
  • Excel Timers Need things to repeat on a timer? This shows two methods for creating timers in Excel which we can use for countdowns, uptime counters, dashboard updates, etc. The first method ...
    Posted Sep 18, 2020, 8:25 AM by Craig Hatmaker
  • Best Practices: Integrity Checks Integrity checks are tests for model conditions that, if present, require alerting anyone using the project. Integrity checks can save our careers. integrity checks alert modelers to errors that should ...
    Posted Sep 29, 2020, 5:00 AM by Craig Hatmaker
Showing posts 1 - 5 of 110. View more »
Subpages (2): Index References
Comments