System Tables
Millennium includes several tables that store system information rather than data or lookup table information. This information is needed by various components of the system in order to perform their tasks. While it may be helpful for the system administrator to be familiar with the general purpose of these tables for troubleshooting and maintenance situations, most users will not need to be aware of their nature or existence in order to successfully use Millennium.
For SQL sites, system tables are located in the databases as described below. For Oracle sites, the system tables are all located in the data database, either under the milldata or the millreports tablespace.
milldata (or the name that your institution uses for the data database)
account_services_log
alerts
autoid
edirectoryinfo
fieldlst
filters
keyvalue
login_audit
merchant_account
online_import_mapping
pendingid
prototype_name
serialreceipt_run
sorts
sysinfo
systemplate
table_options
themes
userlist
user_settings
userview
utility_settings
viewlist
we_clientid
millreports
memory_definitions
memory_field_definitions
report_clipboard
report_criteria
report_descripts
express reports
report_options
report parameters
report_printers
report_servers
account_services_log
This table in the primary data database contains a history of failed Paya Payment Solutions processing attempts. A row is written for each attempt to store account information in the vault that fails, and for each credit card or bank draft payment processing attempt that fails. All fields are system-generated.
Field Name |
Type (SQL/Oracle) |
Length {Constraints} Default |
Description |
---|---|---|---|
log_key |
numeric/number |
13, 0
|
This system-generated field holds the unique, primary key for the row. |
log_id |
char |
10
|
This field holds the Id number of the constituent who owns this row, providing a link between this row and all others in all other tables which also belong to the same constituent. (system field) |
log_lnkfil |
char |
2 {'05', '08'}
|
This field holds the file (table) number of either the Gift or Dues table, indicating to which kind of row this Payment row is attached. |
log_lnkkey |
numeric/number |
13, 0
|
This field holds a copy of the primary key field from the primary Gift or Dues row to which this log row is attached. |
log_tender |
char |
6 {'cc', 'bank'}
|
This field holds the tender type of the Gift or Dues row to which this log row is attached. |
log_message |
varchar/varchar2 |
200
|
This field holds the reason for the failed credit card or bank draft processing attempt. (For Example, INVALID C_EXP means the processing attempt failed because the credit card expiration date was expired or in an invalid format. |
log_reference |
char |
10
|
Paya Payment Solutions identifier for the failed credit card or bank draft processing attempt. |
log_errorcode |
char |
6
|
This field holds the code associated with the reason for the failed credit card or bank draft processing attempt. |
log_indicator |
char |
1
|
This field holds the approval status code. If the process failed because of a front end error (Declined), this field is set to 'E'. If the process failed because of a gateway error (Unable to Process) this field is set to 'X'. |
log_userid |
varchar/varchar2 |
30
[suser_sname()] |
The User ID of the operator that submitted the credit card or bank draft for processing. |
log_date |
datetime/date
|
8
[getdate()] |
The date and time of the credit card or bank draft processing attempt. |
alerts
This table in the primary data database contains one data row for each System Alert that has been created and saved by the system administrator.
Indices - alerts
Index | Primary | Foreign | Unique | Fields | Sort |
pk_alerts |
Y |
|
Y |
alertkey |
ASC |
autoid
This table in the primary data database contains the next available ID number in Millennium. It is read and updated by the software when a new constituent is created and Millennium generates the ID number.
Field Name |
Type (SQL/Oracle) |
Length {Constraints} [Default] |
Description |
---|---|---|---|
autoid |
numeric/number |
10,0
|
This is the next, unused constituent Id number. This information is automatically updated by the system. |
Indices - autoid
Index | Primary | Foreign | Unique | Fields | Sort |
pk_autoid |
Y |
|
Y |
autoid |
ASC |
edirectoryinfo
This table in the primary data database includes information for the Online Constituent Directory email Setup.
Field Name |
Type (SQL/Oracle) |
Length {Constraints} [Default] |
Description |
---|---|---|---|
einfokey |
numeric/number |
13, 0
|
This system-generated field holds the unique, primary key for the row. |
einfoemail |
varchar |
200
|
Return email address. |
einfomessagetype |
char |
6
['user', 'pwd'] |
email message type; 'user' for user name, 'pwd' for password. (system field) |
einfomessage |
varchar |
4000
|
email message contents. |
Indices - edirectoryinfo
Index | Primary | Foreign | Unique | Fields | Sort |
pk_edirectoryinfo |
Y |
|
Y |
einfokey |
ASC |
express_reports
This table in the millreports database contains information about any reports that have been either saved as an Express Report or contains prompted criteria lines or saved parameters. This includes the name of the criteria upon which the Express Report is based, plus a record of all the settings, prompts or any other variables that were used the last time the owner ran the report. This table will also contain similar information about any reports that contain prompted criteria statements or saved parameters, and that have been run at least one time.
Field Name |
Type (SQL/Oracle) |
Length {Constraints} [Default] |
Description |
---|---|---|---|
report_name |
varchar/varchar2 |
50
|
The name (title) of the report criteria with which these report settings are associated. |
report_table |
varchar/varchar2 |
30
|
The name (system name) of the report criteria with which these report settings are associated. |
report_category |
varchar/varchar2 |
50
|
The name of the report library for the criteria. (Biographical, Financial, etc.) |
report_owner |
varchar/varchar2 |
30
|
The User ID of the user who created the saved set of criteria to which this Express report is linked. |
char |
1
|
'X' if a report is saved as an Express Report.
'R' if a report has prompted criteria lines, is run and is not saved as an Express Report.
Once a report has been saved as an Express Report, it cannot be changed to a non-Express Report unless the user deletes the Express Report definition and reruns the criteria without saving as an Express Report.
Prior to Millennium version 7.6, report_type = 'T' for all Express Report rows. Once an Express Report is re-saved, the value of this field is changed to 'X'. |
|
report_created |
datetime/date |
8
|
The date and time that they report was created. |
report_edit_date |
datetime/date |
8
|
The date and time when the report was last edited. |
report_edit_user |
varchar/varchar2 |
30
|
The Millennium UserId of the person who last edited the report. |
report_run_date |
datetime/date |
8
|
The date and time when the report was last run. |
report_run_user |
varchar/varchar2 |
30
[' '] |
The Millennium UserId of the person who last ran the report. |
report_select_time |
varchar/varchar2 |
10
|
The amount of time that the last selection process took. |
report_format_time |
varchar/varchar2 |
10
|
The amount of time that it took the formatting software to process, the last time that the report was run. |
report_total_time |
varchar/varchar2 |
10
|
The total amount of time that it took for the report to be completed, the last time it was run. |
report_records |
varchar/varchar2 |
10
|
The number of data rows that were selected by the last run of the report. |
report_export_time |
varchar/varchar2 |
10
|
The amount of time spent preparing the export worktable, the last time that the report was run. |
report_export_owner |
varchar/varchar2 |
30
|
The Millennium UserId for the person who 'owns' the saved export worktable. |
report_export_table |
varchar/varchar2 |
30
|
The name of the saved export worktable. |
report_export_dbase |
varchar/varchar2 |
30
|
|
report_groups |
char |
6
[' '] |
|
report_mgp1 |
numeric/number |
10, 0
[67108863] |
The maintenance security associated with the report group. |
report_mgp2 |
numeric/number |
10, 0
[67108863] |
The maintenance security associated with the report group. |
report_agp1 |
numeric/number |
10, 0
[67108863] |
The access security |
report_agp2 |
numeric/number |
10, 0
[67108863] |
|
report_descriptions |
varchar/varchar2 |
500
|
The free-text description of the report. |
report_user |
varchar/varchar2 |
30
|
The Millennium UserId for the person who 'owns' this report. |
report_settings |
varchar/varchar2 |
4000
|
This field tracks all of the variables and settings that the owner of the Express Report may use or edit via Express Reports. These settings and variable values are remembered and defaulted into the FasTabs in Express Reporting and will be used again the next time the report is run, until or unless the owner edits and uses different values.
If a report is not an Express Report, but contains prompted criteria statements, and has been run at least one time, this field will track the values that were given to those prompted criteria statements the last time the report was run. These values may be edited the next time the report is run. |
Indices - express_reports
Index | Primary | Foreign | Unique | Fields | Sort |
pk_express_reports |
Y |
|
Y |
report_name, report_type, report_category, report_user, report_groups |
ASC |
express_reports01 |
|
|
|
report_table, report_owner |
ASC |
fieldlst
This table is used as a resource by several components of the software. Each row describes one of the fields from the database. There is a row for every field in every table in the database. Basic information about each field such as the data type, whether it can contain nulls, and foreign dependencies is included for each. This table is used by the Sorts, Filter, Millennium Reporter, Customizer, and Advanced Search features of Millennium.
Field Name |
Type (SQL/Oracle) |
Length {Constraints} [Default] |
Description |
---|---|---|---|
table_name |
varchar/varchar2 |
30
|
The name of the data table (or search) where the field 'lives'. |
column_name |
varchar/varchar2 |
30
|
The system name of the field. |
datatype |
varchar/varchar2 |
30
|
The nature of the field (datetime, date, integer, numeric, number, money, varchar/varchar2, varchar2, etc.) |
prec |
numeric |
5, 0
|
This is the precision for the field. |
scale |
numeric |
10,0
|
This is the scale the field. |
length |
numeric |
5, 0
|
The size of the field in characters. |
nullable |
numeric |
5,0
|
This indicates whether the field may or may not be null. |
identcol |
numeric |
5,0
|
This field is generated by SQL and used as an identifier. The key fields are examples. |
reference |
varchar/varchar2 |
30
|
If the field being described in this row has a foreign key constraint (it is driven by a lookup table), this will identify that lookup. |
column_alias |
varchar/varchar2 |
30
|
This field is the user-defined alias (if any) to be shown in the MR pull-down field list, the list of Available Columns on the Clipboard Setup page and the list of Available Columns in all of the Define Results Display applets.
SQL query tools can be used to change the field alias. In addition, if the label of a field is modified via the Custom Display Designer or by using any of the Define Results Display applets, the system will update the contents of this field to reflect the new label. |
displaytype |
varchar/varchar2 |
1
|
This field indicates to the system the type of data entry component the field will use (check box, text box, list box, etc.) |
colid |
numeric |
5, 0
|
This is the position within its table for the field described in this row. |
syscolind |
varchar/varchar2 |
1
|
This is used to flag a field as a system-use field that should not be made available to insert, update or delete forms. |
Indices - fieldlst
Index | Primary | Foreign | Unique | Fields | Sort |
pk_fieldlst |
Y |
|
Y |
table_name, column_name |
ASC |
filters
This table in the primary data database contains descriptions of filters defined by each user. Every user can have his/her own defined filter for each table in Millennium. Each row in this table defines a single criteria statement for one of those Filters. Therefore, if the Filter has multiple lines of criteria, there will be multiple rows in the Filter table that together comprise the entire definition of the Filter for that user for the specified table.
Field Name |
Type (SQL/Oracle) |
Length {Constraints} [Default] |
Description |
---|---|---|---|
user_name |
varchar/varchar2 |
30
|
The User ID for the operator to whom this filter belongs. If the user is sa or MILLORA, then user_name ismillennium_admin. |
filter_name |
varchar/varchar2 |
30
|
This field holds the name that the filter was given. |
file_number |
varchar/varchar2 |
2
|
This field shows the number of the data table this filter defines. |
line_number |
numeric/number |
4,0
|
This field identifies to the system where the criteria defined in this row fits in relation to the other criteria statements for the complete Filter definition. |
criteria |
varchar/varchar2 |
150
|
This field shows the screen version of the criteria statement (spelled out in English). |
details |
varchar/varchar2 |
200
|
This field contains the field name, a coded version of the comparison and the object for the select statement. |
primarykey |
numeric/number |
13, 0
|
This is the primary key field, automatically generated by the system on insert. |
profiles_active |
char |
1
|
If this filter is the active one for the data table on which it is defined, the value of this field will be 'Y'. If not, then the value of this field will be 'N'. |
snapshot_active |
char |
1
|
If this filter is the active one for the data table on which it is defined, when the data table is shown in Snapshot View, then the value of this field will be 'Y'. If not, then the value of this field will be 'N'. |
link_file |
varchar/varchar2 |
2 |
If this filter is defined for data rows that link to a primary data row, then this field will hold the table number to which the records link. For examples, if a filter is defined for attribute rows that are linked to Basic Data, then the value of this field will be 00. If a filter is defined for attribute rows that are linked to Education, then the value of this field will be 07. |
Indices - filters
Index | Primary | Foreign | Unique | Fields | Sort |
pk_filters_primarykey |
Y |
|
|
primarykey |
ASC |
uq_filters |
|
|
Y |
user_name, filter_name, file_number, line_number |
ASC |
keyvalue
This table in the primary data database stores system options and settings that are not stored in the sysinfo system table, and user options and settings that are not stored in the userlist system table. For example, Serial Receipts uses entries in this table to store site information for Receipt printing as well as the Issue New Receipts, Reprint Receipts, and Void Receipts screens defaults for individual users.
Field Name |
Type (SQL/Oracle) |
Length {Constraints} [Default] |
Description |
---|---|---|---|
kvuser |
char |
10
|
The name of the Millennium user if the row is used to store a user option or setting. kvuser is set to (System) if the row stores a system option or a system setting. |
kvkey |
char |
45
|
The system-generated key word for the row’s system or user option or setting. |
kvvalue |
varchar/varchar2 |
4000
["] |
The value associated with the row’s system or user setting. |
Indices - keyvalue
Index | Primary | Foreign | Unique | Fields | Sort |
pk_keyvalue |
Y |
|
Y |
kvuser,kvkey |
ASC |
login_audit
The login_audit table in the primary database contains a history of all attempts to log on to the Millennium database. If the Audit user login attempts system option is set to Yes, then a row is written for each log on attempt, both successful and failed. If this system option is set to No and the number of failed log on attempts before locking users out of Millennium (Log In Lockout system option) is set to one or more, then a row is written only for each failed log on attempt made.
Field Name |
Type (SQL/Oracle) |
Length {Constraints} [Default] |
Description |
---|---|---|---|
audit_key |
numeric/number |
13, 0
|
This is the primary key field, automatically generated by the system on insert. |
user_name |
varchar/varchar2 |
30
|
The User ID of the user who attempts to log on to Millennium. |
IP_address |
char |
40
|
The IP address of the machine that the user is utilizing when attempting the log on |
login_date_time |
datetime/date |
8
getdate() |
The date and time the log on attempt is made. |
login_success |
char |
1
|
Set to 1 if the log on attempt is successful. Set to 0 if the log on attempt fails. |
login_mobile | char |
1
[' '] |
Set to Y if the user is logging on to the system by using Mobile Millennium. |
Indices - login_audit
Index | Primary | Foreign | Unique | Fields | Sort |
pk_login_audit |
Y |
|
Y |
audit_key |
ASC |
login_audit01 |
|
|
|
user_name |
ASC |
login_audit02 |
|
|
|
IP_address |
ASC |
memory_definitions
The memory_definitions table in the millreports database holds parameters needed by the Summaries Utility and the Years Utility, to create data rows in the Summaries (name of the table in the database: memories) data table. Each row in this table holds those parameters for an individual definition, which the user may retrieve by name (field1) when running the Summaries or Years utilities. The information contained in fields 4 - 10 is interpreted based on the type of definition as identified in field 3. In the chart below, the descriptions of those fields are shown for each of the four possible types of memory definitions, Numeric, Descriptors, Calculations, or Years.
Field Name |
Type (SQL/Oracle) |
Length {Constraints} [Default] |
Description |
---|---|---|---|
field1 |
char |
50
|
The name of the Summary definition. |
field2 |
integer |
10,0
|
The line number. This is reset to 1 for each new type within a definition, and for each new definition. If field3 = Years, then this field will be 1. |
field3 |
char |
30
|
The type of definition. May be: Numeric, Descriptors, Calculations, or Years. The information for this field determine what fields 4 - 10 represent. |
field4 |
char |
30
|
N - Code from the Memory Type lookup table. |
field5 |
char |
30
|
N - Name of total or calculation. |
field6 |
char |
30
|
N - 'A' or 'R' for Add or Replace. |
field7 |
char |
30
|
N - unused |
field8 |
char |
30
|
N - unused |
field9 |
char |
30
|
N - unused |
field10 |
char |
30
|
N - unused |
Indices - memory_definitions
Index | Primary | Foreign | Unique | Fields | Sort |
pk_memory_definition |
Y |
|
Y |
field1, field3, field2 |
ASC |
memory_field_definitions
The memory_field_definitions table in the millreports database holds parameters needed by the Summary Utility when the new rows in the Summaries table will have values for the custom memory lookup fields (memlookup1 through memlookup3), memory campaign year (memcampyr), memory money fields (memmny1 through memmny15), memory date fields (memdate1 through memdate10), memory yes/no flag fields (memyesno1 through memyesno4), memory comment field (memcomm), and memory text fields (memtext1, memtext2). Each row in this table holds extra parameters for each individual memory definition stored in the memory_definitions system table, which the memory_definitions table internally retrieves by memory definition name (field1), line number (field2), and type of memory definition (field3) when running the Summaries utility. The information contained in fields 7 and 8 is interpreted based on the type of memory field as identified in field 4. In the chart below, the descriptions of those fields are shown for each of the seven possible types of memory fields: Lookup, Campaign Year, Money, Date, Yes/No, Comment, or Text.
Field Name |
Type (SQL/Oracle) |
Length {Constraints} [Default] |
Description |
---|---|---|---|
field1 |
char |
50
|
The name of the Summary definition, copied from the memory_definitions table. |
field2 |
integer |
10,0
|
The line number, copied from the memory_definitions table. |
field3 |
char |
30
|
The type of definition. May be: Numeric, Descriptors, Calculations, or Years, copied from the memory_definitions table. Currently, this is set to NUMERIC. |
field4 |
char |
30
|
A classification of the name of the memory field defined. May be LOOKUPNAME, CAMPYRNAME, MONEYNAME, DATENAME, YESNONAME, COMMNAME, TEXTNAME |
field5 |
integer |
10,0
|
A line number. This is reset to 1 for each new field2 value within a definition. |
field6 |
char |
30
|
the name of the Summaries table column |
field7 |
char |
30
|
L - not used Camp -- not used M -'A' or 'R' for Add or Replace D - not used Y - not used Comm- not used T - not used |
field8 |
char |
4000
|
L - lookup table code constant Camp - campaign year constant M -the name of the total, or calculation, or a constant numeric value D -date constant Yes - 'Y' or 'N' Comm - comment constant T - text constant |
Indices - memory_field_definitions
Index | Primary | Foreign | Unique | Fields | Sort |
pk_memory_field_definition |
Y |
|
Y |
field1, field2, field3, field4, field5 |
ASC |
merchant_account
This table in the primary database holds Paya Payment Solutions merchant account information. Data is maintained in this table via the System Options screen, Paya Payment Solutions section.
Field Name |
Type (SQL/Oracle) |
Length {Constraints} [Default] |
Description |
---|---|---|---|
merkey |
char |
12
|
Paya Payment Solutions licensing information: the Key that is associated with this merchant account row. |
merid |
char |
12
|
Paya Payment Solutions licensing information: the Id number that is associated with this merchant account row. |
mername |
char |
60
|
The descriptive name associated with this merchant account row. |
merccsave |
char |
1 {'0', '1'} ['0']
|
A flag to tell the system to allow constituents' credit card and bank draft account information to be saved for future use.
This flag can be set only on the default merchant account. If this row is the default account and this option is On, and then another merchant account row is flagged as the default, the triggers will set this option to Off, on this row, and the user must then set this option to On on the new default merchant account row. |
merdefault |
char |
1 {'0', '1'} ['0']
|
A flag to indicate to the system that this is the merchant account is to be utilized as the default account for credit card payment and bank draft processing.
Only one merchant account row can be flagged as the default. If this row is the default merchant account and another merchant account row is subsequently flagged as the default, the triggers will reset this flag on this row to Off. |
merevents |
char |
1 {'0', '1'} ['0']
|
A flag to indicate to the system that this is the merchant account to be utilized as the account for the credit card payment and bank draft processing of event registration fees.
Only one merchant account can be flagged for use with event registration fees. If this is the row so flagged, and another merchant account row is subsequently flagged as the events merchant account row, the triggers will reset this flag on this row to Off. |
meruserid |
char/varchar2 |
30
[suser_sname()] |
Automatically entered by the system and set to millennium_admin (system field) if the merchant account row was entered through the System Options screen. |
merdate |
datetime/date
|
8
[getdate()] |
The date this merchant account row was last edited. It is automatically entered by the system. (system field) |
mervault |
char |
1
[0] |
The SPS Vault. |
merprimkey |
Numeric
|
13,0
|
The Primary Key. |
Indices - merchant_account
Index | Primary | Foreign | Unique | Fields | Sort |
mer01 |
|
|
Y |
merid |
ASC |
pk_merchant_account |
Y |
|
Y |
merkey |
ASC |
uq_mername |
|
|
Y |
mername |
|
online_import_mapping
This table in the primary data database holds the information needed by the Advanced Data Examiner (ADE) Import tool to import records into Millennium pending tables.
Field Name |
Type (SQL/Oracle) |
Length {Constraints} [Default] |
Description |
---|---|---|---|
mapkey |
numeric/number |
13,0
|
This is the primary key, automatically generated by system at insert |
mapname |
char |
100
|
Name of the map |
millfnum |
numeric |
10,0
|
Field number of the Millennium field that is being mapped |
millfield |
char |
10
|
Name of the Millennium field that is being mapped |
special |
char |
10
['N'] |
Used as a system field by the Advanced Data Examiner (ADE) Import Tool |
infldname |
char |
255
|
Name of the Input File field that the Millennium field is mapped to, or table code of the lookup table that the Millennium field is mapped to, or a constant value that the Millennium field is mapped to. |
infldnum |
numeric |
10,0
|
Field Number of the Input File field that the Millennium field is mapped to |
mapuserid |
varchar |
30
|
Millennium User ID of the user who created the map. Also used as a system field by the Advanced Data Examiner (ADE) |
pendingrownnum |
int |
10,0
|
Used as a system field by the Advanced Data Examiner (ADE) Import Tool |
infilename |
varchar |
255
|
Used as a system field by the Advanced Data Examiner (ADE) Import Tool |
Indices - online_import_mapping
Index | Primary | Foreign | Unique | Fields | Sort |
pk_online_import_mapping |
Y |
|
Y |
mapkey |
ASC |
pendingid
This table in the primary data database contains the next ID number available for use for the Millennium pending tables, when rows are inserted into them via the Advanced Data Examiner Import Tool. It is read and updated by the software when a potential new constituent is created or if an existing constituent's Id number is not included in an external input file.
Field Name |
Type (SQL/Oracle) |
Length {Constraints} [Default] |
Description |
---|---|---|---|
pendingid |
numeric/number |
10, 0
|
This is the next, unused constituent pending Id number. This information is automatically updated by the system. |
Indices - pendingid
Index | Primary | Foreign | Unique | Fields | Sort |
pk_pendingid |
Y |
|
|
pendingid |
ASC |
prototype_name
This table in the primary data database will contain a data row for each Defined Default (also known as a prototype) that is created by any user or by the system administrator. When a default is created, a row is written to the default table associated with the data table for which the default has been created. The prototype_name table will not hold a row for any Defined Defaults that are created via the Data Examiner. Those defaults are directly accessed by the system from the default table associated with the data table and have a User ID of 'ecommerce'.
Field Name |
Type (SQL/Oracle) |
Length {Constraints} [Default] |
Description |
---|---|---|---|
protokey |
numeric/number |
13, 0
|
This is the primary key field, automatically generated by the system on insert. |
protodate |
datetime |
[getdate()] |
This field defines when the last time the prototype was created or changed. |
protouserid |
varchar |
30
|
This field defines what user created the prototype. If this is a System Defined Default, or prototype, protouserid will be set to millennium_admin. |
protoname |
varchar |
100
|
This field holds the name the prototype was given. If a System Defined Default, or prototype, this will be set the System Default. |
protolnkfil |
char |
2
|
This field holds the table number of the data table that the prototype is linked to. For example, if a default is defined for the gifts table, this field is set to '05'. |
protolnkkey |
numeric |
13, 0
|
This key field points to the row in the default table for the data table (for example, def_gifts is the default table for gifts) that the prototype row is associated with. |
protoactive |
char |
1
|
This is a Y/N flag to indicate which prototype is the current active one. |
protorowtype |
char |
6
|
This field holds the number that corresponds to multiple data entry form prototypes, for example, Relation (Constituent, Non-constituent) and Basic Data (Person, Corporation, Other). |
Indices - prototype_name
Index | Primary | Foreign | Unique | Fields | Sort |
pk_prototype_name |
Y |
|
|
protokey |
ASC |
prototype_name01 |
|
|
|
protouserid |
ASC |
prototype_name02 |
|
|
|
protouserid |
ASC |
prototype_name03 |
|
|
|
protolnkkey |
ASC |
report_clipboard
This table in the millreports database stores the criteria rows that are copied to the Main Report Form Clipboard. One row for each line of criteria that is part of the latest Copy to Clipboard action performed by the user will be stored in this table. When the user logs out of Millennium, all rows maintained in this table, for the user, will be deleted.
Field Name |
Type (SQL/Oracle) |
Length {Constraints} [Default] |
Description |
---|---|---|---|
clipkey |
numeric/number |
13,0
|
This is the primary key field, automatically generated by the system upon insert. |
userlogin |
varchar/varchar2 |
30
|
The user name of the person who owns the criteria lines that were copied to the Main Report Form Clipboard. |
modify_date |
datetime/date |
8
|
The date and time the criteria lines copied to the Main Report Form Clipboard were copied or last modified |
criteria |
varchar/varchar2 |
1250
|
The text of the line of criteria that was copied to the Main Report Form Clipboard. |
Indices - report_clipboard
Index | Primary | Foreign | Unique | Fields | Sort |
pk_report_clipboard |
Y |
|
Y |
clipkey |
ASC |
report_criteria
This table in the millreports database stores all saved sets of reporting criteria defining Totals or Groups. Each row in this table corresponds to a single line of criteria, and fields within the row serve to identify the rows as part of a unit.
Field Name |
Type (SQL/Oracle) |
Length {Constraints} [Default] |
Description |
---|---|---|---|
criteria_name |
varchar/varchar2 |
50
|
This the user-assigned name for the Total or Group. |
report_type |
char |
1
[' '] |
This flags the criteria for use with any of the Profiles libraries (P) or the Event library (E). |
criteria_type |
char |
1
[' '] |
This indicates whether the criteria is part of a Total (T) or a Group (G). |
created_by |
varchar/varchar2 |
30
['SUSER_SNAME()'] |
This is the User ID for the user who saved the lines of criteria. |
created_date |
datetime/date |
8
[getdate()] |
This is the date on which the criteria was saved. |
line_number |
numeric/number |
5, 0
|
This identifies the position of each line of criteria in the set that has been saved as a unit. |
criteria |
varchar/varchar2 |
1250
|
This is the text of the saved line of criteria. |
Indices - report_criteria
Index | Primary | Foreign | Unique | Fields | Sort |
pk_report_criteria |
Y |
|
Y |
criteria_name, report_type, criteria_type, line_number |
ASC |
report_descripts
The report_descripts table in the millreports database acts as a table of contents and statistician for four different types of tables or files that are part of the Reporting World in Millennium. Each row in report_descripts represents one of these other tables or files. The report_type field in each row in report_descripts identifies the kind of table being described. The possible types are:
- User-defined Criteria tables (U) - These are the created and saved report criteria tables that contain all the criteria statements and other components that comprise a complete set of criteria.
- Template tables (T) - These are the system standard template tables that may be used to create new report criteria.
- Advanced Search query tables (Q) - Each user may "own" one such table that holds the criteria for their most recent Advanced Search.
- HTML Output files (V) - These files hold the .htm results of the run of a report that was sent to an HTML destination, rather than to a printer.
When you use the Millennium Explorer to access the display of an indexed list of criteria via Edit Criteria, to access a report's HTML output via View Report, or a template to use to create New Criteria, the items that are shown in each of those situations are taken from the first column in the report_descripts table. The Explorer will display those items in accordance with the report_type field for each row.
Field Name |
Type (SQL/Oracle) |
Length {Constraints} [Default] |
Description |
---|---|---|---|
report_name |
varchar/varchar2 |
50 |
U - The name of the criteria. (for example, November
Cash Receipts Detail) P - The name of the criteria. (for example, November Cash Receipts Detail) |
report_table |
varchar/varchar2 |
30 |
U - The name of the table. (for example, november_cash_receipts_det1000) P - none |
report_category |
varchar/varchar2 |
50 |
U - The name of the report group. (for example,
Financial) P - The name of the report group. (for example, Financial) |
report_owner |
varchar/varchar2 |
30 |
U - The User ID of the user who created the row.
(for example, abc) P - The User ID of the user who ran the report. (for example, abc) |
report_type |
char |
1 |
U - User-created criteria. P - The report destination is PDF. |
report_created |
datetime/date |
8
|
Q - The date on which the report was created. U - The date on which the report was created. |
report_edit_date |
datetime/date |
8
|
(U only) The most recent date on which the report was edited. |
report_edit_user |
varchar/varchar2 |
30
|
(U only) The user Id who made the most recent edit. |
report_run_date |
datetime/date |
8
|
(U only) The date of the most recent run. |
report_run_user |
varchar/varchar2 |
30
[' '] |
P - The User ID for whom the most recent run was executed. U - The User ID for whom the most recent run was executed. V - The User ID for whom the most recent run was executed. |
report_select_time |
varchar/varchar2 |
10
|
(U only) The amount of time spent performing the selection, the last time this report was run. |
report_format_time |
varchar/varchar2 |
10
|
(U only) The amount of time spent by the 3rd party formatting software, the last time this report was run. |
report_total_time |
varchar/varchar2 |
10
|
(U only) The sum of the select, format, and export times, the last time this report was run. |
report_records |
varchar/varchar2 |
10
|
(U only) The number of rows that were initially selected, minus any that were removed according to duplicate, spouse, and deceased removal options. |
report_export_time |
varchar/varchar2 |
10
|
(U only) The amount of time spent building the export worktable, including name formatting time. |
report_export_owner |
varchar/varchar2 |
30
|
(U only) The User ID for the user who owns the export worktable. |
report_export_table |
varchar/varchar2 |
30
|
(U only) The name of the saved export worktable. |
report_export_dbase |
varchar/varchar2 |
30
|
(U only) The database where the export worktable is stored. |
report_groups |
char |
6
[' '] |
P - The code for the Report Groups lookup table entry that is associated with this row. U - The code for the Report Groups lookup table entry that is associated with this row. V - The code for the Report Groups lookup table entry that is associated with this row. |
report_mgp1 |
numeric/number |
10, 0
[67108863] |
P - The code for the Maintenance 1 field from the Report Groups entry that is associated with this row. Q - The code for the Maintenance 1 field from the Report Groups entry that is associated with this row. T - The code for the Maintenance 1 field from the Report Groups entry that is associated with this row. U - The code for the Maintenance 1 field from the Report Groups entry that is associated with this row. V - The code for the Maintenance 1 field from the Report Groups entry that is associated with this row. |
report_mgp2 |
numeric/number |
10, 0
[67108863] |
P - The code for the Maintenance 2 field from the Report Groups entry that is associated with this row. Q - The code for the Maintenance 2 field from the Report Groups entry that is associated with this row. T - The code for the Maintenance 2 field from the Report Groups entry that is associated with this row. U - The code for the Maintenance 2 field from the Report Groups entry that is associated with this row. V - The code for the Maintenance 2 field from the Report Groups entry that is associated with this row. |
report_agp1 |
numeric/number |
10, 0
[67108863] |
P - The code for the Access 1 field from the Report Groups entry that is associated with this row. Q - The code for the Access 1 field from the Report Groups entry that is associated with this row. T - The code for the Access 1 field from the Report Groups entry that is associated with this row. U - The code for the Access 1 field from the Report Groups entry that is associated with this row. V - The code for the Access 1 field from the Report Groups entry that is associated with this row. |
report_agp2 |
numeric/number |
10, 0
[67108863] |
P - The code for the Access 1 field from the Report Groups entry that is associated with this row. Q - The code for the Access 1 field from the Report Groups entry that is associated with this row. T - The code for the Access 1 field from the Report Groups entry that is associated with this row. U - The code for the Access 1 field from the Report Groups entry that is associated with this row. V - The code for the Access 1 field from the Report Groups entry that is associated with this row. |
report_descriptions |
varchar/varchar2 |
500
|
P - The free text description associated with set of criteria. T - The free text description associated with set of criteria. U - The free text description associated with set of criteria. V - The free text description associated with set of criteria. |
Indices - report_descripts
Index | Primary | Foreign | Unique | Fields | Sort |
pk_report_descripts |
Y |
|
Y |
report_name, report_type, report_category, report_run_user, report_groups |
ASC |
report_options
This table in the millreports database contains all report default options for each user in the system, as set via the Option, Default form within the MR.
In addition, this table will maintain default queue and default printer information for each group and for each user in the system. The default queue and default printer options are set for each group via User Security, Group Maintenance. The default queue and default printer options are set for each user via User Security, User Maintenance or via Options, Report Options form within the MR.
For an Millennium User Group, only the default queue and the default printer information will be maintained in this table.
Field Name |
Type (SQL/Oracle) |
Length {Constraints} [Default] |
Description |
---|---|---|---|
userid |
char |
30
|
This is the User ID for the user or Millennium User Group whose defaults are defined in this row. |
table_codes |
char |
1
['N'] |
This flags the system to display the values only (N) or the codes followed by the values ( Y) within the MR. |
destination |
char |
1
['F'] |
This flags the system to send the report results to a Printer (P), HTML (S), PDF (F), or export (E). |
print_criteria |
char |
1
['N'] |
This flags the system, if set to Yes (Y) to print the criteria when the set of criteria is run. |
save_export |
char |
1
['N'] |
This flags the system, if set to Yes (Y) to save the export worktable that is created by the run of the criteria. |
default_to_name |
char |
1
['N'] |
Not currently in use by the system. |
warn_on_overwrite |
char |
1
['N'] |
Not currently in use by the system. |
format_names |
char |
1
['1'] |
This is the flag signaling the use of the advanced name (1), preferred name (2), or no name (3) in the export worktable. |
construct_sal |
char |
1
['N'] |
This signals whether the salutation name should be constructed Yes (Y) or No (N) |
salutation_code |
char |
6
|
This tells the system the name type to use in construction the salutation name. |
formatted_name_type |
char |
6
|
This tells the system the name type to use for the formatted name. |
password_protect |
char |
1
['N'] |
This indicates whether the criteria is or is not to be password protected. (no longer used) |
deceased |
char |
1
['N'] |
This indicates whether deceased constituents should or should not be included. |
accounting_method |
char |
1
['1'] |
This indicates whether the system should use cash (1), asset (2), or net present values (3). |
spouse_name |
char |
1
['1'] |
This indicates whether spouse names should be combined if both are selected (2), combined if either is selected (3), or never combined (1). |
duplicates |
char |
1
['N'] |
This indicates whether duplicates should be included or excluded. |
address_override |
char |
1
['1'] |
This indicates whether the setting for including an Address in the generic worktable is set to Selected (0), Preferred (1), or None (2). |
home_address_type |
char |
6
['a'] |
If the export worktable uses them, this indicates the Address Type for the address information to be shown in the Home Address columns. |
business_address_type |
char |
6
['b'] |
If the export worktable uses them, this indicates the Address Type for the address information to be shown in the Business Address columns. |
workfile_format |
char |
2
|
This indicates whether the export worktable should be the generic table (0) or a custom layout. |
remove_spouses |
char |
1
['N'] |
This indicates whether one spouse's rows should be removed from the export worktable. |
report_path |
char |
128
[see description] |
This is the path to the report formats.
Defaults to what is entered in System Info, Default Formats Location. |
output_list |
char |
1
['F'] |
This indicates the default output option for this user, either Crystal (F), or Utilities (U). |
export_format |
char |
1
['0'] |
This field identifies the default export format, either Word for Windows (0), Excel (1), Tab Delimited (2), Comma Delimited (3), or ASCII Text (4). |
delimited_export_format |
char |
1
|
This field identifies the default output behavior when no format is selected (no output, tab delimited, or CSV). |
default_UNC |
char |
128
|
This allows the user to specify a default location for Export worktables. |
allow_copypaste |
char |
1
['N'] |
This field is a flag field. If set to 'Y', the Clipboard will be shown and enabled on the Report Form. |
char/varchar2 |
30
|
This field is used to hold the name of the queue to which the report will default for this user or this user group |
|
char/varchar2 |
256
|
This field is used to hold the descriptive name of the printer to which the report will default for this user or this user group. |
|
new_ocd_users |
char |
1
['N'] |
This field is a flag field. If set to 'Y', then the Online Constituent Directory users who do not have to change passwords the next time they log on (core1passw = 'N') will be removed from the group of constituents initially selected by the report criteria. |
Indices - report_options
Index | Primary | Foreign | Unique | Fields | Sort |
pk_report_options |
Y |
|
|
userid |
ASC |
report_parameters
This table in the millreports database holds defined, standard parameters that can be included with any designed criteria. The creation and maintenance of information in this table must be performed outside of Millennium, and is entirely at the option and responsibility of the site. The following chart shows the structure that the Millennium Reporter will expect and require, if you choose to use this custom reporting option.
Field Name |
Type (SQL/Oracle) |
Length |
Constraints |
Description |
---|---|---|---|---|
parameter_name |
char |
45 |
none |
Name of this standard parameter |
default_value |
char |
50 |
none |
This is the initial value of this parameter and will be the final value if the user is not permitted to alter the default value. |
prompt_user |
char |
1 |
'Y' or 'N' |
If 'Y', the user is prompted to enter a new value for this parameter when the criteria is executed. Otherwise, the default value is used. |
prompt_text |
char |
120 |
none |
This is the text used to prompt the user to change the default value if prompt_user = 'Y'. |
char |
30 |
valid lookup table-driven field name |
This is the name of a lookup table-driven data field that is associated with this parameter. If this field is populated and prompt_user = 'Y', then, when the report is run, the user will be presented with a list box of valid table codes or values from the lookup table that the data field references. For example, if this field is populated with 'coreconst', then the user is presented with a list box of the valid codes or values from the constituent_types lookup table. He or she then chooses from this list.
On filling the list box with valid lookup table codes/values, a code of "*" representing any value will also be added. This information must be in accordance with the data in the special_type field. If not, the information in the special_type field will take precedence. |
|
special_type |
char |
1 |
'C' - checkbox |
This field is used to signal the nature of the data that will be accepted for this parameter. A check box only accepts a 'Y' or 'N'. Year, Month,
and Day displays a calendar and only accepts a year, month, or day. An
'F' prompts for a full date. |
default_update |
char |
1 |
'Y' |
When criteria is saved with a stored parameter, a default value is also saved with the criteria. When the report is run, the default update flag is checked. If it is set to 'Y', the default is displayed from the report_parameters table instead of the default saved with the criteria. |
Indices - report_parameters
Index | Primary | Foreign | Unique | Fields | Sort |
pk_report_parameters |
Y |
|
|
parameter_name |
ASC |
report_printers
This table in the millreports database holds the system information for all reporting printers, including the name of the printer, the Queue to which the printer is assigned, the path to the printer, and the specific printer driver. Each set of printer information that is entered into System Info will generate one row in the Report Printers table.
Field Name |
Type (SQL/Oracle) |
Length {Constraints} [Default] |
Description |
---|---|---|---|
queue_desc |
varchar/varchar2 |
30
|
This is the free text description of the Queue. |
printer_desc |
varchar/varchar2 |
30
|
This is the free text description of the printer to be used by the Queue. |
printer_path |
varchar/varchar2 |
256
|
This is the location of the printer as it is recognized by the computer. |
printer_name |
varchar/varchar2 |
90
|
This is the name of the printer, as it is known to the computer. |
printer_driver |
varchar/varchar2 |
256
|
This is the printer driver that is used by the printer. |
Indices - report_printers
Index | Primary | Foreign | Unique | Fields | Sort |
pk_report_printers |
Y |
|
Y |
queue_desc printer_desc |
|
report_servers
This table in the millreports database holds the system information for all reporting Queues, including the name of the Queue, the name of the machine on which the Queue is located, the path to the Queue, and the names of the databases (millwork and the data database) that the Queue is utilizing. This table is located in the millreports directory.
Oracle version of report_servers - This table holds the system information for all reporting Queues, including the name of the Queue, the name of the machine on which the Queue is located, the path to the Queue, and the names of the databases instance that the Queue is utilizing. If your site is licensed to use Visual Analyzer, this table also holds the system information for the QlikView Server and Qlikview documents location.
Field Name |
Type (SQL/Oracle) |
Length {Constraints} [Default] |
Description |
---|---|---|---|
server_desc |
varchar/varchar2 |
30
|
The name of the Queue - This is the free text description of the Queue, used to identify it to users. |
report_server |
varchar/varchar2 |
30
[' '] |
This is the name of the computer where the database resides. |
report_path |
varchar/varchar2 |
128
{' '] |
This is the full UNC path to the queue. |
report_workdb |
varchar/varchar2 |
30
|
This field is not in use at the present time. |
report_database |
varchar/varchar2 |
30
[' '] |
This is the name of the data database (for example, milldata) |
report_millreports |
varchar/varchar2 |
30
|
This field is used in replicated database situations to identify the server to which the IIS is pointing. (SQL only) |
report_preview |
char |
1
['N'] |
This field is not is use as of Millennium 7.8 |
server_type |
char |
1 {'k','O','E','Q'} ['Q'] |
This field is used to indicate whether the information in this row is applicable to a reporting queue (Q), or a QlikView Server (K). Values 'E' and 'O' are not in use at the present time. |
Indices - report_servers
Index | Primary | Foreign | Unique | Fields | Sort |
pk_report_servers |
Y |
|
Y |
server_desc, report_server, server_type |
ASC |
serialreceipt_run
The serialreceipt_run table stores receipt runs generated by the Issue New Receipts process or when a manual receipt is entered. One record corresponds to one receipt run. This is a linking table that links one or more receipts in the serialreceipt table to the 'run' that generated the receipt.
Field Name |
Type (SQL/Oracle) |
Length {Constraint} [Default] |
Description |
---|---|---|---|
srunkey |
numeric/number |
13,0 |
The primary key field. This field holds a permanent "time stamp" of the precise time and date the row was created. This uniquely identifies a row within the table. (system field) |
srunnumber |
char |
10
[ " ] |
Run number |
srunstrtnm |
char |
10
[ " ] |
Start receipt number |
srunendnum |
char |
10
[ " ] |
End receipt number |
srunstrtky |
numeric/number |
13,0
[ 0 ] |
Start receipt key |
srunendky |
numeric/number |
13,0
[ 0 ] |
End receipt key |
sunrundte |
datetime/date |
|
Run date |
sruncount |
number/numeric |
8,0
[ 0 ] |
Receipts count |
srunpaycnt |
number/numeric |
8,0
[ 0 ] |
Payments count |
srunmanual |
char |
1
['N'] |
Manual receipt flag |
srunuser |
char |
30
[ " ] |
Run user |
srunprefix |
char |
4
[ " ] |
Run prefix |
Indices - serialreceipt_run
Index | Primary | Foreign | Unique | Fields | Sort |
pk_serialreceipt_run |
Y |
|
Y |
srunkey |
ASC |
sorts
This table in the primary data database contains the descriptions of the Sorts defined by each user. Every user can have his/her own defined sort for each table in Millennium. Each such sort will generate a row in this table.
Field Name |
Type (SQL/Oracle) |
Length {Constraints} [Default] |
Description |
---|---|---|---|
userid |
varchar/varchar2 |
30
|
This is the user name of the user who owns this Sort definition. If the user is sa or MILLORA, then userid is millennium_admin. |
filenum |
varchar/varchar2 |
2
|
This is the number of the table that the Sort defines. |
sortfield1 |
varchar/varchar2 |
10
|
This is the name of the field to be used as the basis of the primary sort order. |
order1 |
varchar/varchar2 |
1
|
This indicates whether sortfield1 is to be ordered ascending (A) or descending (D). |
sortfield2 |
varchar/varchar2 |
10
|
This is the name of the field to be used as the basis of the second level of sort order. |
order2 |
varchar/varchar2 |
1
|
This indicates whether sortfield2 is to be ordered ascending or descending. |
sortfield3 |
varchar/varchar2 |
10
|
This is the name of the field to be used as the basis of the third level of sort order. |
order3 |
varchar/varchar2 |
1
|
This indicates whether sortfield3 is to be ordered ascending or descending. |
sortfield4 |
varchar/varchar2 |
10
|
This is the name of the field to be used as the basis of the fourth level of sort order. |
order4 |
varchar/varchar2 |
1
|
This indicates whether sortfield4 is to be ordered ascending or descending. |
sortfield5 |
varchar/varchar2 |
10
|
This is the name of the field to be used as the basis of the fifth level of sort order. |
order5 |
varchar/varchar2 |
1
|
This indicates whether sortfield5 is to be ordered ascending or descending. |
primarykey |
numeric/number |
13, 0
|
This is the primary key field, automatically generated by the system on insert. |
sort_name |
char/varchar2 |
30
|
This field holds the name of the sort |
profiles_active |
char |
1
|
If this sort is the active one for the data table on which it is defined, the value of this field will be 'Y'. If not, then the value of this field will be 'N'. |
snapshot_active |
char |
1
|
If this sort is the active one for the data table on which it is defined, when the data table is shown in Snapshot View, then the value of this field will be 'Y'. If not, then the value of this field will be 'N'. |
link_file |
varchar/varchar2 |
2 |
If this sort is defined for data rows that link to a primary data row, then this field will hold the table number to which the records link. For examples, if a sort is defined for attribute rows that are linked to Basic Data, then the value of this field will be 00. If a sort is defined for attribute rows that are linked to Education, then the value of this field will be 07. |
Indices - sorts
Index | Primary | Foreign | Unique | Fields | Sort |
pk_sorts_primarykey |
Y |
|
|
primarykey |
ASC |
uq_sorts |
|
|
Y |
userid, sort_name, filenum |
ASC |
systemplate
This table in the primary data database contains the data strings and other information that define the way that data is displayed to each user at your institution. As delivered, this table will be populated with a complete set of default definitions for the various display modes for each data table and situation. Each row in the table defines one display situation. If your institution chooses to modify a display by using the Custom Display Designer, additional rows will be added to this table to contain those site-custom definitions. When looking to this table for display definitions, Millennium will first look for a custom definition. If none exists, it will use the standard default.
In addition, each user on the system may define a Single Line display for each data table. Each of those Single Line definitions is maintained in a row in this table.
Field Name |
Type (SQL/Oracle) |
Length {Constraints} [Default] |
Description |
---|---|---|---|
syskey |
numeric/number |
13, 0
|
This is the key (identifier) field for this row. |
sysworld |
char |
30
|
If the display string is used for a user's One Screen View display, then the value of this field is 'Profiles'. If the row is information that is used for displaying data display and maintenance forms, then the value of this field is the world within Millennium in which the display string is used. |
sysuser |
varchar/varchar2 |
30
|
If this is a One Screen View display string, then this is the Id of the sure who owns the One Screen View. Otherwise, this field is set to NULL for all rows. |
sysdefault |
char |
1
|
This flags the row as being a standard, Millennium default data maintenance or display form or One Screen View (Y) or a site-defined customized one (N). |
sysdispnm |
varchar/varchar2 |
30
|
If this is a One Screen View display string, then the value of this field is 'onescreen'. If the row is information that is used for displaying data display and maintenance forms, then the value of this field is the display name for the table. |
systable |
char |
4
|
The number of the table described in this row.
If this is a One Screen View display string, then this field will be set to NULL. |
sysmode |
varchar/varchar2 |
30
|
The mode of display being described in this row. The possible modes are: LONG MINI SNAP ECOMM ECOMMDIA Special ONESCR
If this is a One Screen View display string, then this field will be set to NULL. |
systype |
char |
6
|
For those tables which may be displayed in different ways (for example, Basic Data has different displays for individuals, corporate, and other constituent types, giving data displays for the main and the allocation portions) or has different displays (for example, linked attribute vs. non-linked attribute displays) this field provides an indicator of which version of the displays is being described by this row.
If this is a One Screen View display string, then this field will be set to NULL. |
sysstring |
varchar/varchar2 |
4000
|
If this string defines the display for a data maintenance or data display form, then this field is a text field that contains the string that defines the display. Elements of the display are separated by pipes. Each element begins with the label, a colon separator, special formatting instructions if they exist (such as bold, right justified, etc.), display position, a caret separator, the field number (as it is returned from the database by the dll), and the pipe indicating the end of that element.
If this string defines a user's One Screen View, each 8 character block represents a data table box on display. The first characters specify the data box row number. The next set of character, L, R, or W, specify the location of the data box. The next two characters specify the table number. For example, 00 specifies the corebio table. The next two characters specify the height in number of lines. For example, 06 specifies 6 lines.
Example: <Location><Table Number><Number of Lines> 01L0008 where 01 is the first row of the data box, L is a data box on the left of the view, 00 is the corebio table, and 08 is the height of the table in lines. |
Indices - systemplate
Index | Primary | Foreign | Unique | Fields | Sort |
pk_systemplate |
Y |
|
Y |
syskey |
ASC |
systemplate02 |
|
|
|
systable |
ASC |
table_options
This table is holds information about table and data displays throughout Millennium. A row exists for every data table and special display, such as Giving Trends, in Millennium’s Profiles World.
Field Name |
Type (SQL/Oracle) |
Length {Constraints} [Default] |
Description |
---|---|---|---|
options_tablenum |
char |
2
|
The data table number or data display number as it is known to the system. For example, the Basic Data table has an options_tablenum = '00’. Giving Trends has an options_tablenum = '91’. (system field) |
options_name |
varchar/varchar2 |
30
|
The name of the data table as it exists in the database or the name of the display as it is known to the system. For example, the Basic Data table has an options_name = 'corebio’. Giving Trends has an options_name = 'gifts’. (system field)
|
options_display |
varchar/varchar2 |
30
|
The name of the table as it displays in Millennium. For example, the Basic Data table displays as 'Basic Data’. |
options_removed |
char |
1
['0'] |
A flag to indicate if the data table HAS been removed from the Millennium display. If a table has been removed, then options_removed = '1’. If it has not been removed, then options_removed = '0’. |
options_removable |
char
|
1
|
A flag to indicate if the data table CAN be removed from the Millennium display. If a table can be removed, then options_removable = '1’. If it cannot be removed, then options_removable = '0’. Basic Data, Name, Address, Relation cannot be removed from the Millennium display. (system field) |
Indices - table_options
Index | Primary | Foreign | Unique | Fields | Sort |
pk_table_options |
Y |
|
Y |
options_tablenum |
ASC |
themes
This table in the primary data database stores the My Millennium Appearance settings for each user.
Field Name |
Type (SQL/Oracle) |
Length {Constraints} [Default] |
Description |
---|---|---|---|
theme_name |
varchar/varchar2 |
30
|
the name of the theme that is defined by this row. |
theme_user |
varchar/varchar2 |
30
[suser_sname()] |
This is the user Id for the user whose settings are defined in this row.
|
bg_color |
varchar/varchar2 |
20
|
The background color of the display area. |
bg_image |
varchar/varchar2 |
20
|
The url to the image that is applied to the display area, if any. |
menu_font |
varchar/varchar2 |
65
|
The section header and data rows Edit button menu font type. |
menu_color |
char |
20
|
The section header and data rows Edit button menu font color. |
menu_bold |
char |
1 {'N', 'Y'} ['N'] |
If set to Y, the section header and data rows Edit button menu font style will be Bold. |
menu_slant |
char |
1 {'N', 'Y'} ['N'] |
If set to Y, the section header and data rows Edit button menu font style will be Italic. |
head_font |
varchar/varchar2 |
65
|
|
head_size |
char |
15
|
|
head_color |
varchar/varchar2 |
20
|
|
head_bold |
char |
1 {'N', 'Y'} ['N'] |
|
head_slant |
char |
1 {'N', 'Y'} ['N'] |
|
labelfont |
varchar/varchar2 |
65
|
The field labels' font type. |
labelsize |
char |
15
|
The field labels' font size. |
labelcolor |
varchar/varchar2 |
20
|
The field labels' font color. |
labelbold |
char |
1 {'N', 'Y'} ['N'] |
If set to Y, the field labels' font style will be Bold. |
labelslant |
char |
1 {'N', 'Y'} ['N'] |
If set to Y, the field labels' font style will be Italic. |
datafont |
varchar/varchar2 |
65
|
The data's font type. |
datasize |
char |
15
|
The data's font size.
|
datacolor |
varchar/varchar2 |
20
|
The data's font color. |
databold |
char |
1 {'N', 'Y'} ['N'] |
If set to Y, the data's font style is Bold. |
dataslant |
char |
1 {'N', 'Y'} ['N'] |
If set to Y, the data's font style is Italic. |
datahilite |
varchar/varchar2 |
20
|
The Highlight Text font color |
dataaccent |
varchar/varchar2 |
20
|
The Accent Text font color |
secheadfont |
varchar/varchar2 |
65
|
The section header font type |
secheadsize |
char |
15
|
The section header font size. The maximum size allowed is 13pt. |
secheadcolor |
varchar/varchar2 |
20
|
The section header font color |
secheadbold |
char |
1 {'N', 'Y'} ['N'] |
If set to Y, the section header font style is Bold |
secheadslant |
char |
1 {'N', 'Y'} ['N'] |
If set to Y, display the section header font style is Italic |
hilitefont |
varchar/varchar2 |
65
|
The Highlight Text font type. This is the same value as the Data's font type. |
hilitesize |
char |
15
|
The Highlight Text font size. This is the same value as the Data's font size.
|
hilitebold |
char |
1 {'N', 'Y'} ['N'] |
The Highlight Text font style is Bold, if set to Y. This is the same value as the Data's font style.
|
hiliteslant |
char |
1 {'N', 'Y'} ['N'] |
The Highlight Text font style is Italic, if set to Y. This is the same value as the Data's font style.
|
accentfont |
varchar/varchar2 |
65
|
The Accent Text font type. This is the same value as the Data's font type. |
accentsize |
char |
15
|
The Accent Text font size. This is the same value as the Data's font size.
|
accentbold |
char |
1 {'N', 'Y'} ['N'] |
The Accent Text font style is Bold, if set to Y. This is the same value as the Data's font style. |
accentslant |
char |
1 {'N', 'Y'} ['N'] |
The Accent Text font style is Italic, if set to Y. This is the same value as the Data's font style. |
buttonfont |
varchar/varchar2 |
65
|
The Button text font type |
buttonsize |
char |
15
|
The Button text font size |
buttoncolor |
varchar/varchar2 |
20
|
The Button text font color |
buttonbgcolor |
varchar/varchar2 |
20
|
The background color of the button |
buttonbold |
char |
1 {'N', 'Y'} ['N'] |
If set to Y, the Button text font style is Bold. |
buttonslant |
char |
1 {'N', 'Y'} ['N'] |
If set to Y, the Button text font style is Italic. |
evenrowbgcolor |
varchar/varchar2 |
20
|
Each item that is returned by a Search Results Display (Profiles, Event, Circles and so forth) or Constituent List Display (Prospect, My Staff, and so forth) is shown on a separate row, or line. For ease in readability, the colors of the lines will alternate. This is the color of the even numbered rows. |
oddrowbgcolor |
varchar/varchar2 |
20
|
Each item that is returned by a Search Results Display (Profiles, Event, Circles and so forth) or Constituent List Display (Prospect, My Staff, and so forth) is shown on a separate row, or line. For ease in readability, the colors of the lines will alternate. This is the color of the odd numbered rows. |
tblheadfont |
varchar/varchar2 |
65
|
table header font type |
tblheadsize |
char |
15
|
table header font size |
tblheadcolor |
varchar/varchar2 |
20
|
Not used. |
tblheadbgcolor |
varchar/varchar2 |
20
|
table header background color |
tblheadbold |
char |
1 {'N', 'Y'} ['N'] |
If set to Y, the table header font style is Bold. |
tblheadslant |
char |
1 {'N', 'Y'} ['N'] |
If set to Y, the table header font style is Italic. |
navfont |
varchar/varchar2 |
65
|
The Millennium Explorer Menu ( Millennium Explorer) font type |
navsize |
char |
15
|
Not used. |
navbold |
char |
1 {'N', 'Y'} ['N'] |
If set to Y, the Millennium Explorer Menu ( Millennium Explorer) font style is Bold. |
navslant |
char |
1 {'N', 'Y'} ['N'] |
If set to Y, the Millennium Explorer Menu ( Millennium Explorer) font style is Italic. |
navbgcolor |
varchar/varchar2 |
20
|
Not used. |
navregcolor |
varchar/varchar2 |
20
|
The Millennium Explorer Menu ( Millennium Explorer) standard font color. |
navhilitecolor |
varchar/varchar2 |
20
|
The Millennium Explorer Menu ( Millennium Explorer) font color when the item is highlighted |
navactivecolor |
varchar/varchar2 |
20
|
The Millennium Explorer Menu ( Millennium Explorer) font color when the item is selected. |
Indices - themes
Index | Primary | Foreign | Unique | Fields | Sort |
pk_themes_new |
Y |
|
Y |
theme_name, theme_user |
ASC |
user_settings
This table in the primary database holds the Snapshot View settings and the Address Copy to Clipboard feature settings for each user. One entry exists for user Millennium User ID (but not for each Millennium User Group Id).
Field Name |
Type (SQL/Oracle) |
Length {Constraints} [Default] |
Description |
---|---|---|---|
primarykey |
numeric/number |
13, 0
|
This is the primary key field, automatically generated by the system on insert. |
user_name |
char |
30
|
The user Id of the Millennium user whose settings are defined in this table. |
snap_defdisplay |
char |
200
|
a string of table numbers that the system uses to determine which data tables to display when the user selects his or her Snapshot View of the data. For example, if a user's Snapshot View consists of the Basic Data, Address, Attribute and Internet Address data tables, this code will read 0002038189. (89 signals to the system that the string of table numbers has ended) |
snap_sort00 |
numeric/number |
13, 0
|
not used at this time. |
snap_filter00 |
numeric/number |
13, 0
|
not used at this time. |
snap_sort01 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the name table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter01 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the name table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort02 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the address table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter02 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the address table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort03 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the attribute table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter03 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the attribute table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort04 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the relation table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter04 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the relation table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort05 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the gifts table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter05 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the gifts table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort06 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the jobs table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter06 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the jobs table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort07 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the school table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter07 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the school table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort08 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the dues table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter08 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the dues table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort09 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the comments table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter09 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the comments table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort10 |
numeric/number |
13, 0
|
not used at this time. |
snap_filter10 |
numeric/number |
13, 0
|
not used at this time. |
snap_sort11 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the actions table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter11 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the actions table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort12 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the tasks table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter12 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the tasks table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort13 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the media table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter13 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the media table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort14 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the screener table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter14 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the screener table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort15 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the rating table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter15 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the rating table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort16 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the plannedgifts table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter16 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the plannedgifts table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort17 |
numeric/number |
13, 0
|
not used at this time. |
snap_filter17 |
numeric/number |
13, 0
|
not used at this time. |
snap_sort18 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the memories table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter18 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the memories table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort19 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the finance table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter19 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the finance table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort20 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the demogrph table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter20 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the demogrph table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort22 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the correspondence table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter22 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the correspondence table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort24 |
numeric/number |
13, 0
|
This field is not in use at this time. The primary key of the Sort that is applied to the user's Snapshot View of the receipts table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter24 |
numeric/number |
13, 0
|
This field is not is use at this time. The primary key of the Filter that is applied to the user's Snapshot View of the receipts table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort25 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the national table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter25 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the national table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort26 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the phone table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter26 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the phone table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort27 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the research_source table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter27 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the research_source table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort28 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the membership table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter28 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the membership table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort29 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the quidpro table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter29 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the quidpro table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort30 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the pgrating table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter30 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the pgrating table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort31 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the securities table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter31 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the securities table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort32 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the giftinkind table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter32 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the giftinkind table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort33 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the solicitor table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter33 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the solicitor table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort34 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the honoree table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter34 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the honoree table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort37 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the creditcard table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter37 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the creditcard table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort38 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the payments table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter38 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the payments table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort39 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the subscription table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter39 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the subscription table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort40 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the benefits table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter40 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the benefits table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort42 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the proposal table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter42 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the proposal table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort69 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the custombio table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter69 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the custombio table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort70 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the customprospect table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter70 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the customprospect table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort71 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the sustainerpayments table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter71 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the sustainerpayments table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort79 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the contactinfo table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter79 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the contactinfo table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_sort81 |
numeric/number |
13, 0
|
The primary key of the Sort that is applied to the user's Snapshot View of the internetaddress table. If the user's Snapshot View does not include this table, or if a Sort is not applied, then this field will be Null. |
snap_filter81 |
numeric/number |
13, 0
|
The primary key of the Filter that is applied to the user's Snapshot View of the internetaddress table. If the user's View does not include this table, or if a Sort is not applied, then this field will be Null. |
copy_col1 |
char |
11
|
This field holds the name of the first data field in a user's Copy to Clipboard layout definition. If the field references a lookup table and the user chooses to copy out the lookup table's code, then a 'c' will be stored in the eleventh position. If the user chooses to copy out the lookup table's value, then a 'v' will be stored in the eleventh position. This field will be Null if a user does not have a customized Copy to Clipboard layout definition. See Clipboard Setup User Option, Addresses - Copy to Clipboard. |
copy_col2 |
char |
11
|
This field holds the name of the second data field in a user's Copy to Clipboard layout definition. This field will be Null if a user does not have a customized Copy to Clipboard layout definition, or if there is no second column in the layout definition. See copy_col1. |
copy_col3 |
char |
11
|
This field holds the name of the third data field in a user's Copy to Clipboard layout definition. This field will be Null if a user does not have a customized Copy to Clipboard layout definition, or if there are only two fields in the layout definition See copy_col1. |
copy_col4 |
char |
11
|
This field holds the name of the fourth data field in a user's Copy to Clipboard layout definition. This field will be Null if a user does not have a customized Copy to Clipboard layout definition, or if there are only three fields in the layout definition See copy_col1. |
copy_col5 |
char |
11
|
This field holds the name of the fifth data field in a user's Copy to Clipboard layout definition. This field will be Null if a user does not have a customized Copy to Clipboard layout definition, or if there are only four fields in the layout definition See copy_col1. |
copy_col6 |
char |
11
|
This field holds the name of the sixth data field in a user's Copy to Clipboard layout definition. This field will be Null if a user does not have a customized Copy to Clipboard layout definition, or if there are only five fields in the layout definition See copy_col1. |
copy_col7 |
char |
11
|
This field holds the name of the seventh data field in a user's Copy to Clipboard layout definition. This field will be Null if a user does not have a customized Copy to Clipboard layout definition, or if there are only six fields in the layout definition See copy_col1. |
copy_col8 |
char |
11
|
This field holds the name of the eighth data field in a user's Copy to Clipboard layout definition. This field will be Null if a user does not have a customized Copy to Clipboard layout definition, or if there are only seven fields in the layout definition See copy_col1. |
copy_col9 |
char |
11
|
This field holds the name of the ninth data field in a user's Copy to Clipboard layout definition. This field will be Null if a user does not have a customized Copy to Clipboard layout definition, or if there are only eight fields in the layout definition See copy_col1. |
copy_col10 |
char |
11
|
This field holds the name of the tenth data field in a user's Copy to Clipboard layout definition. This field will be Null if a user does not have a customized Copy to Clipboard layout definition, or if there are only nine fields in the layout definition See copy_col1. |
copy_col11 |
char |
11
|
This field holds the name of the eleventh data field in a user's Copy to Clipboard layout definition. This field will be Null if a user does not have a customized Copy to Clipboard layout definition, or if there are only ten fields in the layout definition See copy_col1. |
copy_col12 |
char |
11
|
This field holds the name of the twelfth data field in a user's Copy to Clipboard layout definition. This field will be Null if a user does not have a customized Copy to Clipboard layout definition, or if there are only eleven fields in the layout definition. See copy_col1. |
copy_col13 |
char |
11
|
This field holds the name of the thirteenth data field in a user's Copy to Clipboard layout definition. This field will be Null if a user does not have a customized Copy to Clipboard layout definition, or if there are only twelve fields in the layout definition. See copy_col1. |
copy_col14 |
char |
11
|
This field holds the name of the fourteenth data field in a user's Copy to Clipboard layout definition. This field will be Null if a user does not have a customized Copy to Clipboard layout definition, or if there are only thirteen fields in the layout definition. See copy_col1. |
copy_col15 |
char |
11
|
This field holds the name of the fifteenth data field in a user's Copy to Clipboard layout definition. This field will be Null if a user does not have a customized Copy to Clipboard layout definition, or if there are only fourteen fields in the layout definition. See copy_col1. |
copy_col16 |
char |
11
|
This field holds the name of the sixteenth data field in a user's Copy to Clipboard layout definition. This field will be Null if a user does not have a customized Copy to Clipboard layout definition, or if there are only fifteen fields in the layout definition. See copy_col1. |
copy_col17 |
char |
11
|
This field holds the name of the seventeenth data field in a user's Copy to Clipboard layout definition. This field will be Null if a user does not have a customized Copy to Clipboard layout definition, or if there are only sixteen fields in the layout definition.
See copy_col1. |
copy_col18 |
char |
11
|
This field holds the name of the eighteenth data field in a user's Copy to Clipboard layout definition. This field will be Null if a user does not have a customized Copy to Clipboard layout definition, or if there are only seventeen fields in the layout definition. See copy_col1. |
copy_col19 |
char |
11
|
This field holds the name of the nineteenth data field in a user's Copy to Clipboard layout definition. This field will be Null if a user does not have a customized Copy to Clipboard layout definition, or if there are only eighteen fields in the layout definition. See copy_col1. |
copy_col20 |
char |
11
|
This field holds the name of the twentieth data field in a user's Copy to Clipboard layout definition. This field will be Null if a user does not have a customized Copy to Clipboard layout definition, or if there are only nineteen fields in the layout definition. See copy_col1. |
headers |
char |
100
|
A string of '0's and '1's to tell the system to either display (1) or not display (0) the section header for a table that is included in the user's Snapshot View of the data. Note that this option is applied individually to each data table in his or her Snapshot View. |
separators |
char |
100
|
A string of '0's and '1's to tell the system to either display (1) or not display (0) the record separators for a table that is included in the user's Snapshot View of the data. Note that this option can be applied to each data table individually. Note that this option is applied individually to each data table in his or her Snapshot View. |
copy_match |
char |
1 {'0' or '1'} ['0'] |
If a user's Copy to Clipboard layout definition includes fields from the Internet Address data table and the user chooses to match Address to Internet Address by Utilization, the value will be 0. If the user chooses to match Address to Internet Address by Type, the value will be 1. See Clipboard Setup User Option, Addresses - Copy to Clipboard. |
popup_menus
|
char |
1 {'0' or '1'} ['0'] |
If the user wants to include pop-up menus in his or her Snapshot View of the data, this field will be set to '1'. If not, this field will remain set at '0'. Note that this option applies to all of the data tables included in the user's Snapshot View; it cannot be set per individual table. |
linked_data |
char |
1 {'0' or '1'} ['0'] |
If the user wants to include linked data in his or her Snapshot View of the data, this field will be set to '1'. If not, this field will remain set at '0'. Note that this option applies to all of the data tables included in the user's Snapshot View; it cannot be set per individual table. |
Indices - user_settings
Index | Primary | Foreign | Unique | Fields | Sort |
pk_user_settings |
Y |
|
|
primarykey |
ASC |
userlist
This table in the primary data database includes information about each user in Millennium including group information, next transaction numbers, defined displays and display options. This is the information that is maintained and displayed via Tools, System Upkeep, User Security. This table also stores user password information.
Field Name |
Type (SQL/Oracle) |
Length {Constraints} [Default] |
Description |
---|---|---|---|
user_name |
char |
30
|
This is the user Id for the user whose settings are defined in this row. |
user_date |
datetime/date |
8
[getdate()] |
This is the date on which this row was last updated. |
user_postuser |
char |
30
[suser_sname()] |
This is the User ID of the operator who last performed an edit to this row. |
user_group |
char |
1
['A'] |
This is the SQL group for the user_name (not the operator who entered the data for this row.) |
user_gtnum |
numeric/number |
10, 0
[1] |
This is the next Gift Transaction Number that should be used when this operator inserts a new Gift data row. |
user_dtnum |
numeric/number |
10, 0
[1] |
This is the next Dues Transaction Number that should be used when this operator inserts a new Dues data row. |
user_defdisplay |
char |
200
|
This field holds a list of the table numbers in the order that they should be displayed according to this user's Defined Display preferences. Leading zeros are used when appropriate to list the table numbers and when this definition does not use all available table numbers, the number 98 is used as a placeholder. |
user_shortlong |
char |
100
|
This field holds a string of 0's and 1's - one for each data table, shown in order. These track whether the user last displayed each table in Short (0) or Long (1) or Mini (2) display mode. |
user_sort |
char |
104
|
This field holds a string of 0's and 1's - one for each data table, shown in order. These track whether the user last displayed each table with the Sort On (1) or Off (0). |
user_filter |
char |
104
|
This field holds a string of 0's and 1's - one for each data table, shown in order. These track whether the user last displayed each table with the Filter On (1) or Off (0). |
user_info |
char |
200
|
This field holds a string of 0's and 1's to track User Options that are currently active for the user. These include the Transaction Display Options, and the Matching Options. |
char
|
200
|
The first digit indicates the user's Lookup table permissions with 0 = none, 1 = select, and 2 - full. The second and third digits indicate the user's method of Membership Processing with 28 = by Membership, 08 = by Dues, and 05 = by Giving (Gift option not yet available).
For a user group, the fifth, sixth, and seventh digits indicate the Display Mask settings for social security numbers and bank account numbers respectively, with 0 = System Default Mask, 1 = No Mask, 2 = Mask all but the last 4 digits, and 3 = Mask all digits. |
|
user_id## |
char |
10
|
If the user is also a constituent on the system, this field holds the constituent Id. |
user_sql_group |
char |
30
|
This is the name of the Database group/role. |
user_comm |
char |
255
|
This is a free text comment that may be associated with this User ID. |
user_logontime |
datetime/date |
30
|
This is the most recent date and time that this user logged on to the system. |
user_logofftime |
datetime/date |
30
|
This is the most recent date and time that this user logged off of the system. |
user_crdate |
datetime/date |
30
[getdate()] |
This is the date on which the user information row was created. |
varchar |
240
|
This field will hold the oldest of the four previous passwords. (encrypted) |
|
user_password2 |
varchar |
240
|
This field will hold the second oldest of the four previous passwords. (encrypted) |
user_password3 |
varchar |
240
|
This field will hold the third oldest of the four previous passwords. (encrypted) |
user_passchngdt |
datetime |
|
This field will hold the date the password was last changed. |
user_passchngnow |
char |
1
['N'] |
This Y/N flag indicates whether the user must change their password at next login. |
numeric/number |
13,0
[0] |
The primary key, from the alerts system table, of the last alert that was displayed to this user. This indicates to the system that this user has seen the alert referenced by this key, and to not show this alert again to this user. |
|
user_qlikview |
char |
1
['0'] |
If this user is a Visual Analyzer user, the value of this field is set to '1'; else it is set to '0' |
user_qlikview_admin |
char |
1
['0'] |
If this user is a Visual Analyzer administrator, the value of this field is set to '1'; else it is set to '0'. |
char |
1
['0'] |
If this user is a Millennium system administrator, the value of this field will be set to '1', else it is set to '0'. |
|
user_password4 |
varchar |
240
|
This field will hold the user's current password (encrypted).
|
user_theme |
varchar |
25
['Blue'] |
This field holds the user's Millennium Display theme option - Green, Orange, Blue, Red, or Custom. This option is set on the Display Theme page. |
user_outlook |
char |
20 |
This field will hold the user's Millennium and MS Outlook Integration settings as follows: Character - 0/1 - Enable Outlook Integration flag Character - 0/1 - Synchronize at login flag Character - 0/1 - Synchronize before logoff flag Character - 0/1 - Synchronize when opening My Tasks Character - 0/1 - Synchronize every X minutes is checked Integer - Character - 0/1 - if Always use Millennium data is selected, set to 0. If Use data with latest timestamp is selected, set to 1 Integer - |
char |
1
['0'] |
This field holds a code that determines the user's access WealthEngine. If the user is allowed to perform only WealthEngine imports, the value of this field is set to 1. If the user is allowed to perform only WealthEngine search, the value of this field is set to 2. If the user is allowed to perform both WealthEngine imports and searches, the value of this field is set to 3. If the user is not allowed to perform WealthEngine imports or searches, the value is set to 0. |
|
user_link_sort |
char |
20 |
This field holds a string of 0's and 1's - one for each kind of linked data (for example, Attributes linked to Basic Data) that can be sorted, shown in order. These track whether the user last displayed the linked data with the Sort On (1) or Off (0). |
user_link_filter |
char |
20 |
This field holds a string of 0's and 1's - one for each kind of linked data (for example, Attributes linked to Basic Data) that can be Filtered, shown in order. These track whether the user last displayed the linked data with the Filter On (1) or Off (0). |
user_show_site_footer |
char |
1 {'N' or 'Y'} ['Y'] |
This field holds the user's option to display or to not display the Community Brands footer frame at the bottom of each display page. Each user sets this option on the Display Theme page. |
user_we_clientid |
char |
30
|
For sites that use Named User Accounts to access WealthEngine, this field holds the WealthEngine Account Name that is assigned to the user. |
user_pinboard |
varchar/varchar2 |
255
["]
|
This field is not in use at this time. |
user_qvgrp |
char |
30
|
If this user is a Visual Analyzer user, this field is the Qlikview Group to which he or she belongs. A site can create special Groups, through Group Maintenance, just for Visual Analyzer users. |
char |
1
|
This field holds the Serial Receipting options for the user |
Indices - userlist
Index | Primary | Foreign | Unique | Fields | Sort |
pk_userlist |
Y |
|
Y |
user_name |
ASC |
userview
This table is in the primary data database used by Millennium as a translation table between the userlist and the viewlist. It describes which Views in the viewlist table apply to which user groups based on a coded View name. Each SQL user group that has been defined on your system will generate one row in this table. This table tracks the Views that are to be associated with the Select, Update, and Delete functions for each data table for each SQL user group. It also tracks whether the group has permission to Insert rows in each of the data tables.
Taken together, the uviews fields 1-6 hold three View codes for each data table. The first of the three holds the View code for the select permission, the second holds the View code for update permissions, and the third holds the View code for delete permission. Each of the uviews fields stores the set of three View codes for 14 of the data tables. Thus, uviews1 might begin with cor000cor000cor000nam000nam000nam000add000add000add000 and so on.
Field Name |
Type (SQL/Oracle) |
Length {Constraints} [Default] |
Description |
---|---|---|---|
uv_user |
char |
30
|
This is the SQL user group name. (Example: mill) |
uviews1 |
char |
252
|
This field holds the Views that are to be associated with data tables 0 through 13. |
uviews2 |
char |
252
|
This field holds the Views that are to be associated with data tables 14 through 27. |
uviews3 |
char |
252
|
This field holds the Views that are to be associated with data tables 28 through 41. |
uviews4 |
char |
252
|
This field holds the Views that are to be associated with data tables 42 through 55. |
uviews5 |
char |
252
|
This field holds the Views that are to be associated with data tables 56 through 69. |
uviews6 |
char |
252
|
This field holds the Views that are to be associated with data tables 70 through 83. (Reserved for future growth.) |
uvinsert |
char |
84
|
This field holds a string of Y's or N's, one for each data table, listed in order, to indicate whether this group does or does not have permission to insert data rows into this table. |
Indices - userview
Index | Primary | Foreign | Unique | Fields | Sort |
pk_userview |
Y |
|
Y |
uv_user |
ASC |
utility_settings
This table is in the primary data database and is used by Millennium Custom Utilities Page.
Field Name |
Type (SQL/Oracle) |
Length {Constraints} [Default] |
Description |
---|---|---|---|
utilname |
varchar/varchar |
120
|
The name of the external application. The name must be unique. |
utilpath |
varchar/varchar |
250
|
The path to the external application. This will function as a hyperlink. |
utildescr |
varchar/varchar |
2000
|
A free-text description of the external application. |
utilpassword |
varchar/varchar |
240
|
Not available for use at this time. |
Indices - utility_settings
Index | Primary | Foreign | Unique | Fields | Sort |
pk_utility_settings |
Y |
|
Y |
utilname |
ASC |
viewlist
This table in the primary data database serves the same purpose to the userview table that a lookup table does for a data table. The userview table stores a code for a View name. The viewlist stores the decoded name and table number for all of the codes representing Views.
Field Name |
Type (SQL/Oracle) |
Length {Constraints} [Default] |
Description |
---|---|---|---|
vlist_code |
char |
6
|
This is the code used to identify a View. This code is used in the uview1-6 fields in the Userview table, and consists of a three letter table prefix, followed by three digits. (Example: cor000) |
vlist_tnum |
char |
2
|
This is the number of the table that is the source for the View. |
vlist_name |
char |
30
|
This is full name of the View. |
Indices - viewlist
Index | Primary | Foreign | Unique | Fields | Sort |
pk_viewlist |
Y |
|
Y |
vlist_code |
ASC |
we_clientid
This table in the primary data database contains information for the WealthEngine Logon for sites that use Named User Accounts to access WealthEngine. Maintaining this WealthEngine information in Millennium allows Millennium to log on and connect to WealthEngine for the user.
Field Name |
Type (SQL/Oracle) |
Length {Constraints} [Default] |
Description |
---|---|---|---|
client_id |
char |
30
|
This field contains the WealthEngine Account Name entered in System Options. |
client_password |
char |
240
|
This field contains the WealthEngine password for the Account Name.The Millennium user who is associated with the WealthEngine Account Name sets and changes his or her password in WealthEngine, and then records this password on the WealthEngine Information page in My Millennium. (encrypted). |