What to put in Settings Table

[Fred Boer]

Hello:

I was updating a version number for my application, and I decided to create
a "Settings" table. So now I have a table "Tbl_Settings", with two fields
"Setting_ID" and "VersionNumber". Nothing special about this, true, but it
set me to wondering, "What else could I store in here that might be
useful?"... So, out of curiosity: do you use such a table? What do *you*
store in it?

Thanks!
Fred Boer

 

[Guest]

Fred,

I don't personally use one for my db, but I can certianly see advantages. I
would include the date you upgraded the version as well as two memo fields
for 1-Upgrades from the last version and 2-Known remaining issues. You could
update the "known issues" field as you come across items that need
addressing. Then you could refer to this in the future when you want to roll
out an upgrade.

I would also consider adding a field that tracks who was responsible for the
version upgrade (if applicable).

Maybe I should add one of these to my db! Hope this helps.

Aaron G
Philadelphia, PA

 

[Jeff Conrad]

in message:

I was updating a version number for my application, and I decided to create
a "Settings" table. So now I have a table "Tbl_Settings", with two fields
"Setting_ID" and "VersionNumber". Nothing special about this, true, but it
set me to wondering, "What else could I store in here that might be
useful?"... So, out of curiosity: do you use such a table? What do *you*
store in it?

Hi Fred,

For my personal application that is sold to businesses, I include the Product
Number, name of the business, and the path to their logo which then shows
up on all reports. This however, may not be applicable to your situation.