I have an mObj class to represent MS Access database tables in my
VB.net project. It handles all table schema stuff like adding columns,
setting properties of columns etc. For example, I have a property in
mObj called AllowBlanks. This is mapped to the 'Required' property of
a MS Access db column.
I have code in the 'Set' statement of the AllowBlanks property to
change the Access column's 'Required property' to whatever the user
submits as 'value' I am using ADOX to work with Access, example:
Private _BlanksAllowed As Boolean
Public Property AllowBlanks() As Boolean
Get
Return _BlanksAllowed
End Get
Set(ByVal value As Boolean)
Dim con As ADODB.Connectio n = DAL.GetADODBCon
Dim db As New ADOX.Catalog
con.Open()
db.ActiveConnec tion = con
db.Tables(_Pare ntMobj.Name).Co lumns(_Name).Pr operties("Nulla ble").Value
= value
con.Close()
_AllowBlanks = false
End Set
Should I have this code here or in a separate function? If I keep it
in the Set statement, how will I know if the code failed or succeeded
when I set the value from a form later on? If it was in a function, I
could have it return false if the code failed.
Keeping the code in the Set statement makes my form code easier to read
mObj.AllowBlank s = True. But I don't understand how I can test if this
is succsesful in my code.
Having the code in a function would be more code in my forms:
SetAllowBlanks( mObj, True), but I could handle a failure if the
function returned false.
How have you all handled Set statements that could provoke an error?
VB.net project. It handles all table schema stuff like adding columns,
setting properties of columns etc. For example, I have a property in
mObj called AllowBlanks. This is mapped to the 'Required' property of
a MS Access db column.
I have code in the 'Set' statement of the AllowBlanks property to
change the Access column's 'Required property' to whatever the user
submits as 'value' I am using ADOX to work with Access, example:
Private _BlanksAllowed As Boolean
Public Property AllowBlanks() As Boolean
Get
Return _BlanksAllowed
End Get
Set(ByVal value As Boolean)
Dim con As ADODB.Connectio n = DAL.GetADODBCon
Dim db As New ADOX.Catalog
con.Open()
db.ActiveConnec tion = con
db.Tables(_Pare ntMobj.Name).Co lumns(_Name).Pr operties("Nulla ble").Value
= value
con.Close()
_AllowBlanks = false
End Set
Should I have this code here or in a separate function? If I keep it
in the Set statement, how will I know if the code failed or succeeded
when I set the value from a form later on? If it was in a function, I
could have it return false if the code failed.
Keeping the code in the Set statement makes my form code easier to read
mObj.AllowBlank s = True. But I don't understand how I can test if this
is succsesful in my code.
Having the code in a function would be more code in my forms:
SetAllowBlanks( mObj, True), but I could handle a failure if the
function returned false.
How have you all handled Set statements that could provoke an error?
Comment