The pop-up menus on the title bars of each table (also referred to as Section Headers) will now contain a list of all available prototypes (defaults). When the user selects a default from this list, the selected default will automatically become the active default and will be utilized when inserting a new data row. This listing is not available on the pop up menus accessible via the edit buttons on each individual record.

If the user changes his or her password, or the system administrator changes a password for a user, Millennium will automatically update the passwords that are stored in any supporting report files to the new password. Millennium will also automatically update the password field in any rows owned by the user in the assignments table. If the Generic Import utility is scheduled to run in an Unattended Mode using the user's log in credentials, these credentials will have to be manually updated to reflect the new password.

The display of real-time alerts is system-wide and is set by the system administrator in System Upkeep, System Alerts (Browser Interface) or System Configuration, System Alerts (Windows Interface). Determine a start date and time,an expiration date and time, and the message to display to all logged in Millennium users. 'Turn on' the alert by setting it to active. Millennium will check for an active alert every three minutes and display this alert to all logged in Millennium users one time. Users select OK in order to proceed in Millennium. Only one alert can be active at any one time. Alerts that have expired will be automatically deleted from the system.

Sites can choose to display 'Spouse' or 'Spouse/Partner' as the label for the yellow Spouse button. This option is system-wide and is set by the system administrator in Millennium System Options.

HTML templates will no longer be used for Millennium display screens. All screen displays will should be displayed via 'Customizer'; all customizations to the screen displays should be made using the Custom Display Designer.

Additional items have been added, and some changes have been made to the captions of the Millennium Explorer items.

Sun Java will be required for use with Millennium. MS Java will no longer be supported. Microsoft is no longer updating MS Java, it is an added security risk, and Sun Java has become the standard.

The keystroke combination ALT-D will not work in Millennium if Internet Explorer 7 is your interface.   Internet Explorer 7 uses this particular combination to give focus to the Address Bar.

Error installing Queue as a Service on Windows XP

Temporary search tables remain in database after user ends session

Load Results not functioning on Search Page

Logon screen cursor does not focus on User ID field

"Cursor not focusing on Name/ID field"

Space bar hot key not functioning

Advanced Search-First selected value invisible when editing in the list of criteria

Permissions out of sync following upgrade to 7.5

When a new Basic Data row is inserted, the triggers will automatically populate the corecfae field with the contents of the table_cfae field of the constituent_types table if CAE Type field on the Basic Data insert form is blank. The user can change the value of corecfae on update. The conversion to Millennium 7.6 will not insert CAE codes into the table_cfae field. Sites will manually do this after the conversion completes.

If you perform a Profile or a Correspondence Search and no constituents who match the search criteria are found, the search form will remain populated with the criteria that you previously entered. If multiple constituents match your search criteria and you choose to refine the search, the new search form will be populated with the criteria that was entered for the previous search.

Sites can define, via entries in the relation_pairs lookup table, what relationship types are allowed to be paired. For example, sites can specify that a spouse-spouse relationship is allowed, but a spouse-company relationship is not. Refer to the Appropriate Relationships and the Relation Pairs topics for more detail. The conversion to Millennium 7.6 will read the relation data table and create an entry in the relation_pairs lookup table for each unique relisa-relwhose pair that is found. The conversion will only store one side of the pair. For example, one relation row may have a boss-emp pair and is linked to another row with the corresponding emp-boss pair. The conversion will populate the Is A (relp_isa) field in the Relation Pairs table with 'boss' and the Whose (relp_whose) field in the Relation Pairs lookup table with 'emp', but will not populate the relisa field with 'emp' and the relwhose field with 'boss'. Millennium uses a view on the relation_pairs table so that both sides are available during data entry.   Sites may have to do post-conversion data clean up on the relation_pairs table to eliminate any inappropriate relationship type pairs that may be been converted.

A toggle button has been added to the address data maintenance forms to enable a user to check all effective months at one time, or uncheck all effective months at one time

Allow for the display of 65 characters when displaying attribute name. This functionality applies only to the Customizer displays. All default displays that contain the attribute name will be updated in the conversion to Millennium 7.6. To apply this functionality to your custom displays, each custom display will have to be re-saved by the system administrator.

A phone_type lookup table has been added to the database, and will replace the address_types lookup table functionality for phone table. The conversion to Millennium 7.6 will copy all entries in the address_types table into this new phone_type lookup table. Sites may have to do post-conversion data cleanup on both the phone_type and the address_types lookup tables.

email and web addresses can now be stored in a separate table. This table will display under the address screen. email and web addresses will not have a direct link to a specific address. A new data table (internetaddress) and four supporting lookup tables were added to the database structure. See Database Changes for more information. In the conversion to Millennium 7.6, there is an option to move all existing phone rows with a phone type code that includes the word 'email' or 'www' over to the new internetaddress table

Additional fields from basic data, names, education, attribute, employment and internet address tables have been added to the Customizer to be available for sites to add for a customized Profile Search screen. From address: district. From attribute: Attr Strt, Attr End. From basic data: Gender, Ethnic, Marital, Birth Date. From education: Schl Dept, Schl Strt Yr, Schl End Yr, Campus, Concentration 2, Concentration 3, Concentration 4. From internet address: email.   From employment: Company Name, Industry, Occupation, Status.

If you do not know if the second individual in a relationship is a constituent or a non-constituent, you may begin creating the relationship from the Constituent Relation Insert form. If the second individual is not found in Millennium, a hyperlink is now available on the Relation ID Search form to take you to the Non-Constituent Relation Insert form. Refer to the Non-Constituent Relationships topic for more information.

Sites can set a system-wide option to allow the Pledge Information Form to display when a Match Pledge Transaction is posted. This will let a user specify the payment schedule for a Match Pledge in the same way a payment schedule is specified for a Pledge Transaction.

If a company is set up to match transactions through another constituent (typically a foundation), Millennium will use the matching employer, not the 'Match Through' constituent, as the Matching Company if the Pull Matching Ratios from the Corporation system option is set to 'Yes'. The matching company will not be updated when changes are made to match ratios, match amounts, match due dates, match quids, match guidelines on the 'Match Through' constituent's Basic Data record. Any updates to the 'Match Through' constituent's CorrectGM information will not be applied to the matching company's Basic Data record. A company/match through company relationship will not be created for the matching company and 'Match Through' constituent. If you site wants to continue to apply any updates made to the 'Match Through' constituent's matching information (either through changes to the Basic Data record or updates to CorrectGM) to the matching company's Basic Data record, and continue to create company/matching company relationships, the Pull Matching Ratios from the Corporation system option must be set to 'No'. See the Basic Data and Matching Gift Data Maintenance topics for more information.

A 'Given By' field has been added to the Post Match Payment insert form. If a matching company is set up to match transactions through another constituent (typically a foundation), the Given By field on the Post Match Payment insert form will be automatically populated by the system with this 'Match Through' constituent's name instead of the matching company's name. If a matching company is not set up to match transactions through another constituent, the system will automatically populate this field with the matching company's name. The Given By field can be overwritten by the user before the match pledge payment is inserted. If the match pledge is owned by a constituent other than the one making the match pledge payment, a gift transaction will be created for the constituent making the payment, and a credit transaction, which reduces the remaining balance on the match pledge by the amount of the gift, will be created for the constituent who owns the match pledge.

Sites can choose to remove tabs, line feeds and carriage returns from comments as they are inserted and updated. This option is system-wide and is set by the system administrator in Millennium System Options.

Ability to search for a constituent by social security number has been removed from the Millennium database Profile, Correspondence, and Registrant searches.

Users will now be able to specify a start day for pledges, in addition to specifying a start year and a start month. This functionality is added to gifts, dues, ecommerce_pending, and phonathon.exe, for pledges, match pledges and sustainer pledges. If a pledge start day is not specified, the default day will be the first day of the month.

Chart of Accounts fields are added to the proposal table so that a proposal can be designated for a specific purpose or restriction . (this field differs from the free text Purpose field (propurpos) on a proposal row).   See Database Changes for the complete list of the fields that were added.

Chart of Accounts fields are added to the plannedgifts table so that a planned gift can be designated for a specific purpose or restriction. (this field differs from the free text Purpose field (planpurpos) on a plannedgifts row). See Database Changes for the complete list of the fields that were added.

The optional Paya Payment Solutions module allows sites to electronically and automatically process transactions made via credit card or bank draft. Sensitive credit card and bank account information will be stored in a 'Vault', which is a series of web services designed to securely store data, in accordance with CISP regulations. For Paya Payment Solutions-enabled sites, credit card and bank account numbers will no longer be stored within Millennium. For non Paya Payment Solutions-enabled sites, both credit card and bank account numbers will be stored in the Credit Card table, credccnum field.

If a transaction has a tender of 'bank', then the check number, ABA/routing number, bank account type, and bank account number fields will be stored in the credit card table, The bank account number will be encrypted. The giftbnktyp, and giftaba fields are no longer supported by Millennium but are still available for use however your site may want to use them. The giftbnkact field is now classified as a system field and is no longer available for data entry or display. The giftchckno field remains available for use in the gift table for transactions given a tender of Check (ck). The conversion to Millennium 7.6 will move those bank account numbers currently stored in the giftbnkact field to the creditcard table, and store them in the credccnum field.

If a transaction has a tender of 'bank', then the check number, ABA/routing number, bank account type, and bank account number fields will be stored in the credit card table, The bank account number will be encrypted. The duesbnktyp and duesaba fields are no longer supported by Millennium but are still available for use however your site may want to use them. The duesbnkact field is now classified as a system field and is no longer available for data entry or display. The dueschckno field remains available for use in the dues table for transactions given a tender of Check (ck). The conversion to Millennium 7.6 will move those bank account numbers currently stored in the duesbnkact field to the creditcard table, and store them in the credccnum field.

More than one credit card row may be attached to a Gift or Dues transaction.

If a gift or dues transaction has a tender of credit card and a linked credit card row exists, changing the tender to another value will no longer automatically delete the linked credit card row.

Enter a transaction with a tender type of Credit Card or Bank Draft. If you cancel the Credit Card or Bank Draft insert, you may now choose to cancel the insert of the entire transaction or just the insert of the Credit Card or Bank Draft row.

Code: bank     Value: 'Bank Draft'

Code: ccd    Value: 'Commercial Checking Draft

Code: csd     Value: 'Commercial Savings Draft'

Code: pcd     Value: 'Personal Checking Draft'

Code: psd     Value: 'Personal Savings Draft'

Financial rows displayed twice in Full Profile view

Constituent Correspondence default without 'Sent By' ID presented in non-constituent form

Defective trigger may delete non-constituent relationships under certain circumstances

Social Security Number field displays as wide row and accepts more than 9 characters

nameplural adds suffix to last name without a space

Double-clicking context menu button presents update form to read-only users

Error code 8152 when inserting value selected in Superlookup applet

Carriage returns cut off text when pasting into Comments field

Link to Existing not functioning when linked-to address has existing link

Updates to Basic Data records with Match Through IDs inserts duplicate relationship

SQL error referencing addrcounty updating a non-US address

Journaling pledge payment with credit for spouse creates payment void for spouse

Cannot change transaction type when updating defined giving default

Cannot update giftasset, giftnetpv in an existing gift transaction.

Giving Tree display totals over $10 million incorrectly

Different Giving Tree settings produce different totals

Second allocation dropped for multiple allocation, on behalf of gift with credit for spouse or otherSecond allocation dropped for multiple allocation, on behalf of gift with credit for spouse or other

Missing hyperlink for on behalf of gift with credit for spouse or other

Deleting on Behalf Of transaction from giver leaves orphaned credit

Pledge payment recorded as gift transaction on joint record under certain circumstances

Deleting on behalf of pledge payment from donor leaves orphaned joint credit

Cannot update/delete giving default with credit transaction gift type.

gift form layouts using giftbnkact not working properly

System attempts to validate credit card number for custom credit card type (incorrect documentation)

Duplicate Match Pledge transaction types in dropdown when adding a Matching Pledge

giftrest field not displaying properly when added to Allocation screen

Inactive Chart of Accounts entries available for selection

Journaling gift after 'journal and add correction' causes transaction to vanish from display

Duplicate Pledge Payment Transaction in dropdown when posting Payment

Unable to UPDATE giftmny1, giftmny2 fields

Cannot convert match potential to match pledge if batch is closed.

Quid pro quo default is not invoked when inserting new gifts via default

giftnonded incorrect on gift with quid after adding joint transaction

Blank default selection screen when attempting to define default

Adding Volunteer to Defined Display adds Dues Detail and multiple Basic Data headers

Auto Login fails for lower or mixed-case User IDs

Assigned to Hyperlink is missing from the linked Actions Tasks row of a Proposal

Lengthy Comments of a linked Actions Tasks row do not display wrapped on the source Proposal row.

Actions Task missing after inserting via Default

Task Due Date incorrectly added to Outlook Calendar

Tracking Attribute filter not functioning

Link to Existing Action on Spouse not functioning when actions linked to attachment

Hyperlinks have been removed from the Events Web Reports: Attendance Listing, Activity Correspondence, Event Correspondence, Registration Listing

Regsolflg, regesolkey fields not populating properly when adding solicitor to registrant

Create New Event screen presented when inserting registrant or guest from Insert menu

When a user with Report Administrator privileges edits a report that they do not own, and saves his or her edits via the 'Save' option (not 'Save As') from the report form Function File menu, ownership of the report is transferred to this Report Administrator user.   The previous owner still has access to the report. If the previous owner has Report Administrator privileges, he can save his changes via the Save option from this file menu and re-assume ownership of the report. If the previous owner does not have Report Administrator privileges, he must save changes via the Save As option from the file menu, and a second copy of the report will then be created. A checkbox captioned 'Report Admin' has been added to Group Maintenance and a check box captioned 'Report Administrator' has been added to User Maintenance. The system administrator can check this box to grant Report Administrator privileges at both the database group and individual user security levels.

If 'None' is the selected Address Preference in criteria, then the addrkey field of the worktable will be populated with 0.

Prior to Millennium version 7.6, a user who did not create, or own, a report had to save a copy of that report before they could view and print the report criteria details. This resulted in multiple copies of the same report, each owned by different users. Users may now view and print report criteria details for reports they did not create and reports for which they do not own their own copy.

An input file that contains a list of Millennium ID numbers can be attached to a set of report criteria. When the report is run, Millennium Reporter will use this list to build an additional criteria statement that will require each data row to have an id number that is on that list in order to be included in the export worktable. This enhancement involves a change to the Millennium Directory structure that is noted in the documentation.

When creating a criteria statement that uses one of 'in the list of', 'not in the list of' or 'never in the list of' comparison operators, a Paste button has been added to the Add and Remove buttons on the Table Display Form Step 2. You may use Paste instead of Add to insert a list of comparison objects into the object text box. The list can be created in a text editor such as Notepad. Each item in the list, including the last, must end with a carriage return, line feed (carriage return, line feed characters are added by hitting Enter or Return on your keyboard). Copy the entire list from your text editor, then select the Paste button on the Millennium Reporter Table Display Form. Your list will be pasted into the object text box. Paste functionality is available for Millennium fields that are not value-based lookup fields.

At the reporting level, users can instruct Millennium Reporter, via a Reporting Option, to insert decrypted values of the Basic Data Social Security Number and Credit Card Number fields into the field_decrypt GENERIC export worktable field. If this option is set to 'ON', reports may run slower than normal, so if reports need to display one of these fields, but you do not want Millennium Reporter to decrypt them, a Millennium-specific User Defined Function is now available for use with Business Objects Crystal Reports. The upgrade to/installation of Millennium 7.6 will install MillCrypt_Crystal.dll into Report Server's Queue folder. Copy and register this file on the Report Development machine; its location will depend on what version of Crystal you are using.

A Millennium-specific User Defined Function for decryption is now available for use with Crystal Reports. The upgrade to/installation of Millennium 7.6 will install MillCrypt_Crystal.dll into the Report Server's Queue folder. Copy and register this file on the Report Development machine to utilize this function when writing and editing your Crystal Report Formats.

If the list of reports is sorted alphabetically by Report Name, then a Letter Navigation toolbar will be available for navigation within the Report List display screen

sa permitted to overwrite GENERIC table when saving worktable

Batch #'s with dashes not functioning in report criteria

'An error occurred attempting to save the report' when saving reports with prompts

EQUAL TO prompt disappears on second run of report

Bypassing IN THE LIST OF Prompt adds blank value to criteria selection box on next run

Prompts missing on second run of report if prompting text is BLANK

Wildcard searches not working on prompted 'Equal To' super lookups in reports

Prompted 'In the list of' super lookups accept invalid responses

Changing the Operator on a Prompted Reply removes prompt

Gray screen when attempting to load criteria

Cannot change format path for Custom Profile report

Formats not available in Format/Utility dropdown

"Cannot insert the value NULL into field 'addrkey' "message running report with user-defined script

Errors when viewing worktables

Reports with prompts automatically saved as Express Reports

Criteria selecting from the attactvity in the attendance table not functioning

New constituents can now be created when utilizing Automatic Update. If a potential constituent cannot be matched to any constituent in the database using the Matching Levels defined in Data Examiner Setup, a new constituent will be created. If a potential constituent matches more than one constituent in the database, this information will be written to a log file for later review.

Your constituents can view and submit changes to their data stored in the Custom Bio and Internet Address tables. The Advanced Data Examiner can update existing Custom Bio and Internet Address records, or create new Custom bio and Internet Address records as they are submitted by constituents or imported by the ADE Import Tool.

Optional add-on components have been added to the Advanced Data Examiner. Users can update existing, or create new, donor, demogrph, finance, media, custom donor, ratings and research_source rows if a site owns the Prospect Tracking component of the Advanced Data Examiner. Users can create new dues and membership rows if a site owns the Membership component of the Advanced Data Examiner. Users can create new registration, event_guest, attendance, event_income, and guest_items rows if a site owns the Events component of the Advanced Data Examiner.

Online Constituent Directory email Setup. Through the use of smart tags, sites can use substitution strings such as username and password in email messages sent to constituents who forget one or both components of their log in credentials. Different messages can be set up for those who need their user name information sent, and for those who need their password information sent. In addition, return email addresses can be set up separately for sending user name information and sending password information.

Millennium users can now control the appearance of the Online Constituent Directory's Header elements, by utilizing the Appearance Setting in Online Directory Setup.

Problems manually updating records with single-letter first names

Sort form presented when attempting to define eDirectory filter

Customizations to OCD Basic Data screen display unwanted wide rows

Online Directory displaying deceased spouse information

OCD search by city returns all results with first three letters

OCD Name changes not displayed in search results

jobsoccup, jobsindust, jobsstatus fields nonfunctional in OCD

OCD search errors out after adding jobsconame to search form

Users prompted to 'click an ID' on OCD search results screen but no IDs displayed

Forgot User ID/Password function is case sensitive when entering email address

Cannot log on to OCD after changing initial password

If the table_cfae code in the constituent_types lookup table for a given table_code is changed, then DataSync will update the corecfae field in the corebio table to reflect this change.

If chart_val in chart_of_accounts lookup table is changed, then DataSync will update the propacctnm field in the proposal table, and the planacctnm field in plannedgifts table to reflect this change.

Added the ability to select the gift restriction for gift transactions. There is a new item on the Options Menu called Use Account Number. If this item is selected, then the gift account number can be mapped to a field in the input file, or manually entered as a constant for all gifts. If this item is unchecked, then the gift restriction can be mapped to a field in the input file, or manually entered as a constant for all gifts. By default, the Use Account Number menu item will be unchecked.

Added the ability to map many additional credit card fields and to map bank account information (if tender is 'bank'). This gift import utility enhancement is the result of the addition of Paya Payment Solutions to Millennium, but sites who do not yet subscribe to this optional module will still have access to these new credit card and bank draft fields.

Added the ability to select the gift restriction for pledge transactions. There is a new item on the Options Menu called Use Account Number. If this item is selected, then the gift account number can be mapped to a field in the input file, or manually as a constant for all pledges. If this item is unchecked, then the gift restriction can be mapped to a field in the input file, or manually entered as a constant for all pledges. By default, the Use Account Number menu item will be unchecked.

Added the ability to input a credit card and bank draft tenders, as well as the default tender of cash. Many credit card and bank draft fields can now be mapped. This phonathon utility enhancement is the result of the addition of Paya Payment Solutions to Millennium, but sites who do not yet subscribe to this optional module will still have access to this new functionality.

Custom Bio and Internet Address tables have been added to the Online Constituent Directory and Advanced Data Examiner. These tables have been added to the Advanced Data Examiner Import Tool as well.

The optional Prospect Tracking, Membership, and Events components added to the Advanced Data Examiner have been added to the Advanced Data Examiner Import Tool as well.

tmprel is a temporary table created by DataSync if user is updating relation table groups. This temporary table is not deleted from the database upon completion of the utility.

Year of Largest Transaction is incorrectly calculated when the user options are set to 'Do Not Include Pledges' AND 'Include Match Paids' AND/OR 'Include Match Due' AND Match Pledges are linked to Pledge Transactions instead of or in addition to Pledge Payment Transactions.

corealmemp and corekwnemp fields are not combined when two Corporations are merged using MergeID

Error when updating blank record in Solicitations lookup table

Generic import utility not functioning

When running Create.exe to create corebio constraints, an error message appears regarding invalid field corepub09.

Default form for Solicitations lookup table entries missing 'Default?' field

Code fields nonfunctional following customization to Chart of Accounts form

Merge ID dialog does not display ID number

Error saving Solicitation lookup entry after adding sol_mand to form

Need to remove Best Software reference from change password error message in User Maintenance

Automation error, blank calendar when running Generic Import Utility

Force users to change password at next log in not functioning

Added a description of the logic the utility uses to match imported Education information to existing Millennium Education rows.

Added a description of a log file that contains errors reported back from Crystal when a report fails to run to completion and the error(s) occurred while Crystal was formatting the report data.

HTML templates no longer supported for Millennium display. References to HMTL templates and/or .mit files have either been removed, or it has been noted that they are no longer supported.

All documentation on the GENERIC worktable needs to be updated to include the new decryption columns.

Added online_import_mapping system table to the documentation.

Updated DataSync.exe documentation to reflect Millennium version 7.5 changes

The format for gift date was incorrectly listed as yymmdd in the specifications for the input file

Edited, and in some places removed, references to Payment Schedules in Expectancy Transactions. The Pledge Information Form does not display when a transaction type of Expectancy is entered.

Previous versions of Millennium had a multi-line checkbox for any fields in the Customizer. In version 7.5 this checkbox has been removed but the documentation still refers to it.

Remove from documentation: "Additional entries to this table may be used, but no verification will be performed."

Menu to define display filters to secondary/linked rows in Prospect>Tracking is active even though help files indicate this feature has not been activated. Since the menu is available and permits filters to be defined, users expect it to be working. Documentation should explain that menus will appear even though they are not functional.

Documentation for v7.5 needs modification to indicate the IIS Worker Process Group (IIS_WPG) or the Network Service account must be present on the Security tab of the Tools folder (X:\Inetpub\wwwroot\mill\tools) with Full Control when running on a Windows Server 2003 IIS server. Running the utility without this group imports the data, but the system cannot create the gmlog.txt file and the last line of the import shows an error. If you deposit the update files in the Tools folder, the error message is, 'Access is denied'.

Clarified documentation on transferring ownership of table objects to another user when deleting a user from the system.

Removed reference to giftpubfl

The description for each of the Published Flags for each table available for Publishing in the Online Constituent Directory is indicating that this option is set with the Name table instead of with each individual table in the Publishing Options. This occurs in the documentation for the schlpubfl, corepublsh, addrpubfl, attrpubfl, relpubfl, jobspubfl, phnpubfl, and commpubfl field descriptions.

Need reference to the limited functionality of custom views used in conjunction with encrypted fields for social security and credit card numbers.

When you remove all privileges to the Address table, you are able to search by constituent id successfully, but you will receive an error when searching by constituent name.

Reset Password feature is not documented.

The Include Joint advanced total option is missing from documentation.

When inserting an additional task after all tasks have been set to complete, the Action Completed On date is not being updated with this latest tasks Completed On date.

Matching Info link produces a blank page.

For use with data entry of constituent and non-constituent relationships; this table links relationship types together to establish what relationship types are allowed to be paired with other relationship types

for use by the phone table, phntype field.

To hold constituent email and web (www addresses). During the conversion to Millennium 76, sites can choose to move their email and web addresses to the internetaddress table. Records in the phone table that have a phone type code that contains 'email' or 'www' will be moved. Once moved, records are deleted from the phone table.

A note about internetaddress_type: As a phone row is moved to the internetaddress table, if the type is not yet in the internetaddress_type table, it is added.

Increased the length of these fields to 200 characters to align with the length of the intaddress field in the internetaddress data table. This provides consistency throughout Millennium for all email address fields.

profilesearch, correspondencesearch, registrantsearch, othereventsearches -increased the length to 200 characters to align with the length of the intaddress field in the internetaddress data table. This provides consistency throughout Millennium for all email address fields.

alertkey

alertstart

alertstop

alerttext

alertacgv

alertcrdt

alertlock

asgnstate increased to 4000, asgncodes increased to 200, asgndecode increased to 600

asgnworktb

asgncoluse

asgnpmdate

asgnactive

ecomlnkfil

ecomdiscod

ecomdiscnt

ecomsol

ecomsolnam

ecomacctnm

ecomchckno

ecomlnkkey

ecomroute

ecombnktyp

ecombanknm

ecomaddrl1

ecomaddrl2

ecomcity

ecomstate

ecomcntry

ecomzip

ecomemail

ecommethod

ecomstatus

ecomccsave

ecomacctty

ecomcustty

ecomssnum

ecomdstate

ecomdlnum

ecombdate

ecomhphone

ecomein

ecomccamt

ecomplgtyp

ecompaycnt

ecompstrty

ecompstrtm

ecompstrtd

ecomlast4

attendance_pending

custombio_pending

customprospect_pending

demogrph_pending

donor_pending

event_guest_pending

event_income_pending

finance_pending

guest_items_pending

internetaddress_pending

media_pending

rating_pending

registration_pending

research_source_pending

credguid

credtender

credroute

credbnktyp

credbanknm

credaddrl1

credaddrl2

credcity

credstate

credcntry

credzip

credemail

credmethod

credprocdt

credstatus

credsave

credlast4

credacctty

credcustty

credssnum

creddstate

creddlnum

credbdate

credhphone

credein

credamount

credchckno

credexdate

spouse_button_label

verus_id

verus_key

verus_allow_ccsave

comment_formatting

ecomm_pub_81

ecomm_upd_81

old_match_through

mp_schedule_auto_create

ecomm_pub_69

ecomm_upd_69

giftpstrtd

giftcrdtyp

giftccfail

duespstrtd

duescrdtyp

duesccfail

eincpend

eincupkey

eincccfail

proprest

propacctnm

propacctno

propacctcf

propacctid

propacctnt

protpacctgp

propacdprt

planrest

planacctnm

planacctno

planacctcf

planacctid

planacctnt

protpacctgp

planacdprt

log_key

log_id

log_lnkkey

log_lnkfil

log_tender

log_message

log_reference

log_errorcode

log_indicator

log_userid

log_date

For use by the giftcrdtyp field in the gift table, and duescrdtyp field in the dues table. These fields, and this lookup table, are not in use at the present time.