>>>A configuration table sounds good to me as long as it covers all your requirements.
>>
>>I think it will unless there is a *new and improved* :) way to manage global settings in a client-server environment
>
>A table is just a storage engine. How and what you store there is up to you.

First, I was thinking of a flat one row settings table but that would limit it to 255 properties (not that I have so many planned but I have something against known limitations cause when they are reached you are too far gone to do anything else easily and all along you knew it was going to come, just IMO)

A few thoughts later...

What are your views about a regular multi-row table with fields for each type of expected value. I know a grid's column can have multiple controls in it, but is it possible that each row of such a grid / column can have different currentcontrol based on say a Flag field which contains the type of expected value for a row, so row one can be a character setting and the txtChar is the current control, on row two it may be chkLogical that is active for the row, ...

Is this possible?

Please advise. Thanks.