I will modernize vb6 and access apps to dot net

Yes. I can assess VB4, VB5 and VB6 projects, provided the available source code, database and dependencies can be reviewed.

Often, yes. Migrating through VB6, VB.NET and then modern .NET is not automatically necessary. I will review the application and recommend the safest route.

Complete source code is strongly preferred. Without it, I can assess the compiled application and database, but reconstruction or reverse engineering must be scoped separately.

Yes. This may include the forms, reports, VBA code, queries and database, or migration to C#, .NET, SQL Server or a modern web application.

That is normally the primary goal. I use a staged approach with documented requirements, testing and comparison against the existing system.

Usually. Replacement depends on the control’s purpose, source availability, licensing and whether a suitable modern equivalent exists.

No. The packages cover an assessment, a representative module or a defined modernization sprint. Complete applications are quoted separately after review.

Yes, where appropriate. Possible targets include ASP.NET Core, Blazor and SQL Server, but the best architecture depends on the users, workflows and deployment requirements.

Usually. Larger migrations can be completed in phases, allowing the existing system to continue operating until replacement modules are tested and accepted.

Yes. However, separating essential migration work from optional new features usually reduces risk and makes testing easier.