Web app design recommendations

Strategic Recommendations

1. Framework: Go with ASP.NET Core Razor Pages

Since you are coming from a "Form-based" background (Access/WinForms), Razor Pages is much more intuitive than MVC.

• Why: In Razor Pages, one file (the Page) handles both the visual layout and the logic, similar to how an Access Form or a VB.NET Form operates.

• Language: Use C#. While VB.NET is supported, 95% of modern web tutorials and libraries are C#-focused.

2. UI Presentation: The "Master-Detail" Pattern

For 28 columns, a "Grid" (spreadsheet style) will be unreadable. Here is the standard modern approach:

• The List View: A searchable, paginated table showing only 4–5 key columns (e.g., Teacher Name, ID, Department).

• The Detail View: When a user clicks "Edit," they are taken to a dedicated page where the 28 columns are organized into Tabs or Accordion sections (e.g., "Personal Info," "Employment History," "Certifications").

• The Child Subform: Place the Child records in a smaller grid at the bottom of the Detail View.

3. Handling Master/Child CRUD

The modern equivalent of "User Controls" in ASP.NET Core is View Components or Partial Views.

• Master: A main form bound to your Teacher model.

• Child: A Partial View that renders the list of Credentials.

• Technology: Use Entity Framework Core (EF Core). It handles the "Master/Child" relationship easily via "Navigation Properties." When you load a Teacher, EF Core can automatically "Include" their 10 credential records.

Razor Pages version first, as its structure feels more familiar to an Access/VB developer.

Official Microsoft Links

• Razor Pages with EF Core Tutorial (Recommended)

  • https://learn.microsoft.com/en-us/aspnet/core/data/ef-rp/intro?view=aspnetcore-9.0&tabs=visual-studio

  • Why: Each page contains both its visual layout and its logic, similar to an Access "Form." This tutorial specifically covers the Master-Detail relationship you need (Instructors with their Courses/Departments).

• ASP.NET Core MVC with EF Core Tutorial

  • https://learn.microsoft.com/en-us/aspnet/core/data/ef-mvc/intro?view=aspnetcore-9.0

  • Why: If you prefer the classic Model-View-Controller separation. It covers slightly more complex scenarios like "Inheritance" in your data models.

Refer links and inputs provided above and decide your migration strategy.

ASP.NET Core MVC and Razor Pages both have advantages and disadvantages, I will not make a suggestion for that.

I will suggest that you learn Entity Framework. EF will make it easier to work with databases.

I suggest the book Pro ASP.NET Core 6 by Adam Freeman but it uses C#.

I think that VS 2022 is capable of generating a CRUD applicaiton for a website. It probably can do that using VB .Net instead of C#. I did generate a web applcation for deliveries that supports a foreign key of shippers. You can create a website to just learn about the stuff.

Converting your MS Access application to ASP.NET, especially with your background in VB.NET, C#, and SQL Server. Let’s break this down and address your key concerns:

ASP.NET Core MVC vs Razor Pages vs Web Forms

• ASP.NET Core MVC is the most flexible and scalable for enterprise-level applications. It’s ideal for complex scenarios like yours with Master/Detail (Parent/Child) relationships.
• Razor Pages is simpler and more page-focused, good for smaller apps or when you want to keep things straightforward.
• Web Forms (VB.NET-style) is outdated and not recommended for new web development projects.

Recommendation: Go with ASP.NET Core MVC. It’s modern, well-supported, and aligns with your need for structured CRUD operations.