7.4 

The Config Table 

7.4.1 Overview 

7.4.1.1 Basic 

operation 

The 

tblCactuShopConfig

 table contains the name of the application variable, 

the value to be stored in it, and an identifier `s' or `n' to designate whether the 

variable is a string or a number. So although every value is stored in the 

database as a string, it is possible to control what type of application variable 

is created from these settings. Also, there is a field that lists the minor version 

of CactuShop in which this variable was added (starting from v5). This should 

make the process of upgrading stores easier, as it will be clear which new 

config settings need to be added. 

7.4.1.2 

Changing config settings 

To edit the config values, go to the 

cactushopback/default.asp

 page and click 

the `Edit Config Settings' link in the centre of the page. This will bring up a list 

of all settings in groups. To change a setting, click the modify button, update 

the value, and submit it. 

Important: the database values held are simply the default values that 

CactuShop will use to create the application variables. It is the application 

variables held in memory that the site uses to generate the pages. If you 

change values in the database using the CactuShop back end, these 

application values are automatically refreshed when you click the submit 

button after changing a value. Remember that if you change config settings 

on the database and upload this, these new settings will not take effect until 

the server reboots or you edit one of the values from the CactuShop back end 

and submit the change. Sometimes, having a stored set of old config settings 

in memory can cause page errors when you upload a database that has 

different config values. To fix this, pass this querystring to any page: 

appvar=reset

. For example: 

http://www.mydomaingoeshere.com/default.asp?appvar=reset

7.4.2 Allowable 

Lengths 

In order to error check database input of strings to ensure they don't exceed 

the length allowed in the database, we can set values to use in error 

checking. These values should be the same as the corresponding field size in 

the database. If you change the size of those fields within the database, you 

should update the allowable lengths to ensure error checking continues to 

work. If overlong string input is made to a database, some older Access 

drivers will just truncate the data string, but SQL Server and newer Access 

drivers will display a database error and the query will fail. All allowable length 

settings are named in the following format: 

[name of database field] + _AL 

So for example 

CD_CardholderCompany_AL

 is the allowable length of the 

cardholder company field. 

55