Hi,
I'm just looking for some feedback here.
I often create tables to store my application options. The table columns are given the option name and there will only be a single row in the table at all times. I'm just wondering if this is a proper way of handling this.
It just seems a bit cumbersome to get the data. I still have to ensure that the table has rows and then get the first row (Dim m_Row as datarow = table.rows(0)) before finally getting the values. It's no problem getting the data but i was just wondering if there is a more straight forward approach.
FYI - These are global settings that all users have access to. Hence the datatable instead of local application settings.
Thanks,
Joel
I'm just looking for some feedback here.
I often create tables to store my application options. The table columns are given the option name and there will only be a single row in the table at all times. I'm just wondering if this is a proper way of handling this.
It just seems a bit cumbersome to get the data. I still have to ensure that the table has rows and then get the first row (Dim m_Row as datarow = table.rows(0)) before finally getting the values. It's no problem getting the data but i was just wondering if there is a more straight forward approach.
FYI - These are global settings that all users have access to. Hence the datatable instead of local application settings.
Thanks,
Joel