TECHNOLOGY HUB
Access and Desktop Application Modernization
Compare desktop renewal, shared data and remote-access options for Access, VB6, Delphi and WinForms applications.
Updated:
Business rules + access
Not sure which software or version you use? Start with your workflow →
SHORT ANSWER
Desktop modernization addresses work tied to one computer when shared data or access from other locations is needed. Local devices and offline requirements determine whether to retain the desktop application, add web access or combine both.
Why now?
| Product / version | Security support ends | Status | Source / checked |
|---|---|---|---|
| .NET Framework 4.8 | No exact day recorded | Date depends on product/distribution | Official lifecycle ↗ |
.NET Framework 4.8: Microsoft's component lifecycle policy applies; .NET Framework 4.8 support follows the lifecycle of its supported Windows host and required servicing level. There is no single end day for every installation. An empty date does not imply indefinite support or security updates for unsupported Windows.
How can work tied to one computer be reorganized?
A cost assessment identifies the actual effort of workstation installation, file collection and repeated data entry. For continuity, document installation, restoration and tasks tied to a particular computer.
AI readiness starts with defined data meanings and access boundaries. Bringing scattered files together does not automatically make their contents correct or suitable for AI use. Test proposed benefits against existing work steps.
Should you improve the desktop platform or move to web and mobile?
| Option | When it may fit | First validation |
|---|---|---|
| Update within the desktop ecosystem | Local devices and offline work determine the requirements | Runtime, operating-system, driver and component compatibility |
| Move selected workflows to APIs, web and mobile interfaces | Shared data or access from different locations has a clear need | Data, authorization and device boundaries for one workflow |
Access, VB6, Delphi and WinForms do not share a single migration path. Select the target around the actual components. Local device work may remain on the desktop while suitable data entry or reporting moves to the web. Assess device-to-app bridges as a separate scope.
When is a smaller change enough? If work depends on local devices and offline operation, a web application may not be the first choice. Improving desktop installation, backups and data sharing may be sufficient.
How should a desktop migration proceed?
- Health check: Record screens, macros, local files, reports, devices and the work users carry out outside the application.
- Incremental changes: Select a bounded workflow; separate data and device responsibilities through explicit interfaces.
- Parallel operation: Have users verify representative tasks in both systems; test reporting, printing, interruptions and synchronization.
- Maintenance: Assign installation, device-bridge, backup, update and user-support responsibilities.
The handover plan should include: A screen and macro inventory, data-transfer checks, device tests and workstation installation instructions.
What determines the cost?
Code and screen volume, existing tests, macros, reports and external connections affect scope. Data volume, file quality, device diversity and acceptable downtime also matter. Offline work and old operating-system requirements need separate assessment.
Compare maintenance and manual-processing costs in the calculator. A legacy health check is a starting point for clarifying the technical scope of file and device dependencies.
How should desktop migration risks be addressed?
- Hidden business rules: Include shortcuts, macros and manual file handling in observation and acceptance scenarios.
- Hardware incompatibility: Run a bounded connection trial with actual devices and drivers.
- Conflicting data: Define ownership, timestamps and conflict resolution for offline records.
- Working habits: Include keyboard workflows, report formats and training needs in the migration schedule.
Frequently asked questions
Is moving an Access application to the web just a data transfer?
No. Queries, forms, reports, VBA code and the work people carry out around files matter alongside tables. Data cleanup, concurrent use and authorization also need design.
Should VB6 or Delphi screens be copied exactly?
First record the tasks, shortcuts and devices people use. A replacement should preserve the required business outcome. Copying a desktop layout directly onto a phone may not produce a usable interface.
Can a WinForms application stay on the desktop?
Yes. Extensive local-device use or offline workflows may justify that choice. A suitable runtime and dependency upgrade should be compared with web migration within the same assessment.
Can a web application use printers, barcode readers or serial ports?
Devices, drivers, protocols and browser conditions need individual tests. A local bridge application may be necessary. Direct browser support for every device cannot be assumed before reviewing the hardware inventory.
Will mobile use continue when the internet connection fails?
Offline operation is separate scope. Define local data, authentication lifetime, synchronization and conflict resolution. Building a web or mobile interface does not by itself provide offline operation.
When can the old desktop application be retired?
Decide after critical tasks, reports, device connections and data acceptance criteria have passed. Archive access, the rollback period and user training also need completion. Opening the new screens is not sufficient.