Generic code for updating business object from dataset - feedback requested

[Lee Ludden]

I have a project where I am converting a very complex MS Access front end to a VB.Net application. There are close to a hundred tables in a SQL database containing mostly but not completely static data that I plan on turning into individual classes. So for each class I have a strongly typed dataset for per table, and a class. Each table has an ID (IDENTITY) field as a unique key. What I am wanting to do is have a generic way of populating and updating each of these classes. Here is what I have so far. First I created a new Attribute class

Then in my class I use this to flag each property with the field that is associated with it in the database (the database is close to 10 years old and has no naming conventions whatsoever).

Imports System.Reflection

Public Class TransportMethod
Implements IEquatable(Of TransportMethod)
Private _code As String
Private _iD As Integer
Private _description As String
Private _requiresAttendant As Boolean

Public Sub New(ByVal row As dsTransportMethod.dtTransportMethodsRow)
    ProcessRow(row)
End Sub

<DataTableSource("TransportMethod")> \_
Public Property Code() As String
    Get
        Return \_code
    End Get
    Protected Set(ByVal value As String)
        \_code = value
    End Set
End Property

<DataTableSource("TransportMethodDesc")> \_
Public Property Description() As String
    Get
        Return \_description
    End Get
    Protected Set(ByVal value As String)
        \_description = value
    End Set
End Property

<DataTableSource("TransportMethodID")> \_
Public Property ID() As Integer
    Get
        Return \_iD
    End Get
    Protected Set(ByVal value As Integer)
        \_iD = value
    End Set
End Property

<DataTableSource("RequiresAttendant")> \_
Public Property RequiresAttendant() As Boolean

[David Mujica]

If you are going to take the time to build new classes for each of your tables, then why are you trying to come up with a generic way of accessing the data ? You are willing to commit the time to create classes, so why don't you take advantage of .NET and write each class specifically for each table ? In the long run, won't you be better off ? Research the topics of DAL (data access layer) and you will get a better idea of how to build an interface to your data. This article has some really good points ... Building an N-Tier Application in VB.NET, in 8 Steps[^] Don't make things harder than they really are :cool: Good luck. :thumbsup: