What question did this study set out to answer?

The aim is to provide a structured approach for deciding the fate of VB6 and Microsoft Access applications.

July 29, 2026Open Access

Extending the Life of and Migrating VB6 / Access Business Apps — A Decision Table for Keep, Wrap, or Replace (archived 2026-07-27)

Key Points

The aim is to provide a structured approach for deciding the fate of VB6 and Microsoft Access applications.
Organized runtime situations into a decision table.
Addressed ACE 32-bit/64-bit compatibility issues.
Outlined risks of multi-user access on shared folders.
Presented a practical procedure for extending application lifecycle.
Identified critical factors for upsizing to SQL Server.
Clarified decision pathways for wrapping or replacing existing applications.

Abstract

How do you decide whether to leave a VB6 application or Microsoft Access business app as-is, extend its life by wrapping only part of it, or replace it outright? This article organizes the runtime situation, the ACE 32-bit/64-bit problem, the risk of multi-user access on shared folders, and upsizing to SQL Server into a decision table and a practical procedure. Archived version of https://comcomponent.com/en/blog/vb6-access-legacy-migration-guide/, as published on 2026-07-27. The live article is maintained and may change after this date. First published 2026-07-04.

AI에게 질문

Bookmark

View Full Paper