Imran Bhatti

Who I am

I'm Imran Bhatti — a developer based in Pakistan who has spent more than a decade building production Microsoft Access and Excel VBA applications for enterprise clients. ActiveX and COM are not a hobby for me; they're the daily tools I use to ship software that businesses actually run on.

LiteView2 grew out of that work. I kept running into the same wall my clients hit: Microsoft deprecated the legacy WebBrowser control without giving VBA developers a usable replacement. The Edge Browser Control in Access 365 exposes four methods. That's not enough to ship a real application. So I built what I needed — and then realised I wasn't the only one who needed it.

Why LiteView2 exists

The story is simple. In 2024 a client asked me to add a dashboard to an Access application that supported their entire field operation. The legacy WebBrowser control rendered Chart.js as broken layouts with constant "script error" popups. The Edge Browser Control couldn't execute JavaScript with a return value, couldn't print to PDF, couldn't access the DOM. Open-source .NET Chromium libraries don't load into VBA either. There was no commercial, COM-friendly WebView2 wrapper that worked reliably across Access, Excel, and VB6.

I spent six months building it. The first version had 40 methods. The version you can download today has 270+ methods, 59 events, a native JSON engine, and registration-free deployment that works on locked-down corporate machines without admin rights. It's used by developers building real applications in real organizations.

How I support LiteView2

LiteView2 is a one-developer product. I am the developer, the support engineer, the documentation writer, and the person who answers your email. That has three practical consequences for you as a customer:

• You email me directly. No tier-one queue. No bot. No ticket number. imran@imranosoft.com goes to my inbox.
• I reply within one business day, every business day. Most replies come the same day. Critical bug reports get fixed before you hear back.
• The roadmap is what customers ask for. If a paying customer needs a feature for a deal, that feature jumps the queue. I don't have a product committee to overrule that.

What this means for you

Buying from a one-developer product is a different deal than buying from a 200-person SaaS company. The honest version of the trade-off:

• What you get: direct access to the person who wrote the code, fast turnaround on bug fixes, willingness to build the feature you need, prices that reflect a one-developer overhead structure.
• What you don't get: a 24/7 enterprise NOC, a sales engineer assigned to your account, a procurement portal, SOC 2 audits, or someone else to escalate to if you don't like my answer.

If those trade-offs are not the right fit for your organization, I would rather you know that before you purchase than after. Email me with your evaluation criteria and I will tell you honestly whether LiteView2 is the right choice — including pointing you elsewhere when it isn't.

How I think about the trial

LiteView2 ships with a 30-day, fully functional trial. All 270+ methods, all 59 events, both registered and registration-free deployment modes, and commercial use are included in the trial. There is no feature lock and no watermark during the trial period.

I don't offer post-purchase refunds because I don't need to — the trial is your evaluation, and it's complete. Try it inside your real use case, with your real Access or Excel app, on your real client's machine. If it works, purchase. If it doesn't, tell me what's missing and either I'll fix it or I'll tell you it isn't going to fit and recommend an alternative.

If 30 days isn't enough for your evaluation timeline, email me before the trial expires and I will extend it. That has never been refused.

Your license keeps working

One reasonable concern about buying from a one-developer product is "what if the vendor goes away?" LiteView2 is designed so that question has a clean answer.

• Your license is perpetual. Once you've purchased, the binary you have continues to work indefinitely.
• Activation works offline. There is no online activation check, no kill switch, no cloud dependency. Your end-users keep running the OCX as long as Windows runs it.
• Royalty-free redistribution. You can ship the OCX with your application to unlimited end-users without per-deployment fees, today and into the future.