It sounds to me that you already see the advantages and disadvantages to
both options. I typically put constants that will rarely change, if ever,
in an include file. If you wanted to have the best of both worlds, you
could create a page that would actually modify this file. You could open
the file with an FSO, parse the contents to find all the constants and the
values, write them back to a form, and have the form, when submitted, create
a new file.
Ray at work
"Bryan Harrington" <ne**@psacake.com> wrote in message
news:Ok*************@tk2msftngp13.phx.gbl...
I'm working on an application that I will make use of "constants". I put
contants in quotes becuase they will change periodically (Logo path, css
path, psw expiration times etc). From a system admin standpoint does it
make sense to put them in a constants file, or put them in a database?
My database argument is that they can be modified by the customer via some
web forms.
My contants include file argument is that they can't be modified as
easiliy by a half wit customer, and there is no database overhead.
Thoughts?
Thanks!