User1120430333 posted
The only way you can do this is with two database connections to the two different databases, with database objects dealing with the two databases and their respective tables.
You have to implement seperation of concerns using a Data Access Layer (DAL) and using the DAO and DTO patterns. You would also be using a
layered style.
Separation of concerns - Wikipedia
Architectural principles | Microsoft Docs
Understanding Separation Of Concern in ASP.NET MVC (c-sharpcorner.com)
The DAO pattern is a DAO on a per table basis that does the CRUD for an individual database table.
Data Access Object (DAO) design pattern in Java - Tutorial Example (javarevisited.blogspot.com)
Data Transfer Object Design Pattern in C# - CodeProject
Chapter 3: Architectural Patterns and Styles | Microsoft Docs
You should understand your various models used in MVC, like the viewmodel as opposed to a data persistence model.
Kinds of Models | DevIQ
Understanding ViewModel in ASP.NET MVC (dotnettricks.com)
You should understand what the link is talking about below.
Understanding Models, Views, and Controllers (C#) | Microsoft Docs
<copied>
An MVC model contains all of your application logic that is not contained in a view or a controller. The model should contain all of your application business logic, validation logic, and database access logic.
A view should contain only logic related to generating the user interface. A controller should only contain the bare minimum of logic required to return the right view or redirect the user to another action (flow control). Everything else should be contained
in the model.
In general, you should strive for fat models and skinny controllers. Your controller methods should contain only a few lines of code. If a controller action gets too fat, then you should consider moving the logic out to a new class in the Models folder.
<end>
The concepts being talked about are being used in ASP.NET MVC solution out on GitHub. The models folder has viewmodel = VM and domain model = DM objects in the Models folder in the ASP.NET MVC project, the presentation layer.
darnold924/PublishingCompany (github.com)
The same kind of concept is being done for a Windows desktop forms solution that is using MVP and a layered style with all layers on the same computer, as opposed to the ASP.NET MVC solution that has a WebAPI sitting between the client-side, and the
WebAPI is doing CRUD with the DAL on the behalf of the client-side.
darnold924/PubComanyWinCore (github.com)
Understanding Basics of UI Design Pattern MVC, MVP and MVVM - CodeProject
HTH
