How to store fixed information

[Andrew Rose]

I have some data I need to store that closely resembles preferences.  It's not going to change often and I'll want to refer to those values when calculating things in other tables.  Like a tax rate container that I might refer to in a calculated field on item price.

Were would I store those?

[Fitch]

It's common practice to create a Preferences table that stores a single record. You can work with that data in various ways - through a relationship, via SQL, via script, or load the data into global fields or variables at startup.