A business-critical spreadsheet with no maintainer
A workbook that quietly runs pricing, payroll or reporting, written years ago by someone who has since moved on. Nobody left can explain what each sheet does.
Documented, repaired, handed back
Working with Excel and VBA?
Most of the workbooks that reach us were built by one clever person over many years, and that person has since left. We read the sheets and the VBA carefully, write down what it actually does, and get it running again without pretending the history isn't there.
What it is
Microsoft Excel is the universal spreadsheet, first released on the Mac in 1985 and on Windows in 1987. It is the tool almost every office worker already has, and the one people reach for when a problem needs numbers in rows and columns.
VBA, short for Visual Basic for Applications, has shipped inside Excel since the mid-1990s. It lets people who are not programmers automate real work, and over the years it has ended up running a surprising share of back-office processes: pricing models, financial consolidations, inventory, commission runs. More recent additions to the suite such as Power Query, Power Pivot, LAMBDA functions and Office Scripts cover much of the same ground with fewer sharp edges.
The honest version
No technology is all upside. This is where Excel and VBA earns its place and where it tends to cause trouble.
Sound familiar?
The Excel and VBA problems that bring people to us, and what you have once each one is fixed.
A workbook that quietly runs pricing, payroll or reporting, written years ago by someone who has since moved on. Nobody left can explain what each sheet does.
Documented, repaired, handed back
A VBA project built for an older version of Office that now fails on open, or raises errors the moment anyone clicks the button.
Working on current Office
Declare statements and ActiveX references written for 32-bit Office that crash or compile-fail the moment IT rolls out 64-bit Office.
Runs on 32-bit and 64-bit
Volatile formulas across whole columns, giant lookup ranges, and array formulas copied far beyond the data. Each change triggers minutes of calculation.
Opens and recalculates in seconds
Formulas reaching across to workbooks on a share that was retired, or to a colleague's desktop that is no longer backed up.
Links traced, replaced or removed
Mark-of-the-web on files from email or SharePoint, group policy settings, or an unsigned project that users no longer have permission to enable.
Signed, trusted and opening cleanly
A workbook that was fine at ten thousand rows now has hundreds of thousands. It is slow, it crashes, and two people cannot edit it at the same time.
Moved to a real database or app
The only version lives on a laptop, emailed around on request, with no history and no off-machine backup.
Versioned, backed up, restore tested
What we do
Call us for one stuck macro, or hand us the whole workbook.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
Yes, and this is most of what we are asked to do with Excel. We read the sheets and the VBA, write down what each part really does, fix the bits that are broken, and hand back a workbook you can safely change.
Usually one of three things. A reference library that moved or was removed, the switch from 32-bit to 64-bit Office needing PtrSafe on Declare statements, or the Trust Center blocking macros from files that arrived by email or from a shared drive.
Often yes. We keep the inputs and outputs people already trust, move the storage and the heavy calculation into a proper database, and give users either a cleaner workbook or a small web form, depending on what fits their day.
The common causes are volatile functions across whole columns, lookup formulas pointing at huge ranges, array formulas copied far beyond the data, and external links to files that are no longer reachable. It is almost always several of these together.
Yes. Declare statements get PtrSafe and the right pointer types, broken references are replaced, ActiveX controls are swapped where needed, and the project is signed so it opens without the warning bar.
Estimates are free. Send the workbook, or describe what it does, and you get a price before any work begins.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: