Hi,
You might create a custom value class that encapsulates value and flag?
Using a DataTable seems a bit of an overkill to me.

Signature
Miha Markic [MVP C#] - RightHand .NET consulting & software development
miha at rthand com
www.rthand.com
> I have been using a HashTable to store name/value pairs, but now I
> need to add a third element (name/value/flag). I still need to be
[quoted text clipped - 9 lines]
> instead? I was originally considering building both tables at the
> same time, but that seems unnecessary.
_eee_ - 04 Mar 2004 20:36 GMT
>"_eee_" <_notme@nomail.com> wrote in message
>> I have been using a HashTable to store name/value pairs, but now I
[quoted text clipped - 4 lines]
>> I'm considering using a DataTable instead of the HashTable since I
>> have to store the values to a database eventually anyway.
>You might create a custom value class that encapsulates value and flag?
>Using a DataTable seems a bit of an overkill to me.
Hi Miha,
You mean slow runtime? I could live with the increased code
complexity of the DataTable as long as it doesn't slow runtime down to
a crawl.
Miha Markic [MVP C#] - 05 Mar 2004 08:48 GMT
Yes, I mean that DataTable has overheads.
Rather use the "holder" class approach.

Signature
Miha Markic [MVP C#] - RightHand .NET consulting & software development
miha at rthand com
www.rthand.com
> >"_eee_" <_notme@nomail.com> wrote in message
> >> I have been using a HashTable to store name/value pairs, but now I
[quoted text clipped - 13 lines]
> complexity of the DataTable as long as it doesn't slow runtime down to
> a crawl.