I have a project coming up where im supposed to upgrade an existing access app to a .net architecture. Im wondering how to design object oriented models from the giant tables and mutliple relationships between them in an ERP like system.
For example, if i have an Order object, the orders table alone has 20+ columns where a lot would translate to normal properties, but an order has multiple foreign keys which all map to their own complex objects like items, customers, supplier etc.
Obviously im also not super familiar with the database and the tables and fields in detail, so do i just translate every colmumn? Do i try to only do the relevant stuff and fix it later if it turns out i need column/property X after all?
Also, since its an upgrade of an access app, the queries are already written and it would be silly not to reuse them, so no Entity Framework i think? Im also wondering how to best initialize them from the database.
What i usually end up with in these bigger systems is something like this to initialize an order completely: get all orders, get all items, get all customers, get all suppliers -> loop through the orders and add the appropriate item/curstomer/supplier from the lists.