Microsoft SQL 2008 is authorized for use with Millennium.

Microsoft Windows 2008 is authorized for use with Millennium.

Java version 1.6.0_16 is the required version for Millennium 7.8. Once you have upgraded to this version, verify that the Java Check for Updates Automatically option is not selected.

Microsoft MapPoint™ 2009 is authorized for use with Millennium. Previous versions of MapPoint™ will not be supported.

Millennium has a new, updated user interface this release. It has new colors throughout the application based on the theme of your choice: Blue, Green, Orange, Red, or Custom. When a theme is selected, it changes the appearance of items on your screen, such as the Millennium Explorer (Millennium Explorer), headings, text, tables, and buttons. Themes can be chosen on the Millennium Display Theme page, which is accessed by using Millennium Explorer, My Millennium>Setup>Appearance. If you have a custom appearance already defined, it is saved under the Custom theme when you upgrade. The conversion will load the new Green theme, which is the default appearance for the Millennium application. If you have a custom appearance already defined, you will need to recreate it, and save it as the Custom theme type.

A new Millennium banner has been added to the top of the application, as well as a Sage footer at the bottom of the application. You cannot turn off the banner, but you can turn off the footer at the user level using Millennium Explorer, My Millennium>Setup>Appearance.

The screens have also been updated with new section headers.These place the data in a group box which includes the new Expand/Collapse feature. This feature allows you to show or hide the data on pages with multiple sections.

The Edit button has been updated to , and the section header hyperlinks have been replaced with the new Edit button . Point to the Edit button to access the pop-up menu to perform additional actions in the application.

These Millennium Explorer item names were changed when the user interface was updated.

• End Session was changed to Log Off
• Reference Other Links>Internet Links was changed to Reference>Other Links>Research Links
• Reference Other Links>Sage/Mill was changed to Reference>Other Links>Sage Resources

• Persistent Worlds functionality has been added to the Browser version of Millennium.
• If you are currently displaying data for a constituent, and you navigate from the Profiles World to another World, or to Circle Definition, you can re-display the data without redoing the search for the constituent. When you click on the Millennium Explorer Profiles item (or click twice if the Profiles World is still 'expanded') , you are returned to the data - displayed in the same format as it was displayed when you navigated away. Profiles World persistence is maintained when you log out and then log back on to Millennium.
• If you are currently viewing information for an Event, you can navigate to another World, or to Circle Definition and re-display the Event information without redoing the Event search. When you click on the Millennium Explorer Events item, you are returned to the same Event information that you were viewing before you navigated away. Events World persistence will cease once you log out of Millennium.

The options to require a minimum number of upper case alphabetical characters and a minimum number of special characters have been added to the Millennium password policy. A System Administrator sets these options on the System Options page.

The number of previous passwords that are checked to verify that a new password has not been used yet, has been increased from three to four.

New fields added to the sysinfo system table to support this functionality:

• password_min_capital
• password_min_special

New fields added to the userlist table:

• user_password4

Millennium can maintain an audit log of successful and failed log on attempts that are made by each user. The option to do so is set on the System Options page. If the option to maintain the log on audit trail is set, then all log on attempts will be written to the login_audit system table. If this option is not set, but the number of allowable failed log on attempts (see Log In Lockout, directly below) is set to one or more, then all log on attempts will be written to the login_audit table as well. If this option is not set, and the system has not been set to lock out users after a specified number of log on attempts, then log on attempts will not be written to the login_audit table.

A new system table has been added to support this functionality:

• login_audit

Firefox users can not use the Upload and Insert, or Upload and Update Attachments functionality.

IE8 users who access Millennium over the internet (as opposed to an intranet) might receive an "Unable to copy Document" error when attempting to Upload and Insert, or Upload and Update, an Attachment. The Security Settings - Internet Zone Include local directory path when uploading files to a server setting must be set to Enable.

IMPORTANT NOTICE for Macintosh users:

• "As Java 1.6+ is not currently supported on 32-bit Macs, we have lost some functionality on the Macs with this release. Mac users of Millennium can still view all data and can do basic data entry. The Mac will not support data entry that involves super lookup tables (attribute type, institutions, solicitations, chart of accounts, gift batch and dues batch); split allocation gifts; event seating; automated membership processing; and editing of event registration, guest, item and attendee rows. Mac users cannot access reporting or customize displays. Mac use is not supported in 64-bit machines. Mac users need to use Safari 4 or Firefox 3.5.2, and the latest version of java for Macs, which is J2SE 5.0 (java version 1.5.0_20) As we move forward with Millennium in future releases, we will be evaluating removing java from the interface and at this time, additional functionality will be supported on the Mac."

The Screen Layouts option has been removed from the System Options page.

The List Templates and List Custom Templates utilities have been removed from the software.

All 65 characters for Lookup table values are now available for display on data display, insert, and update forms. Prior to this release, the system displayed and listed only the first 30 characters unless the Lookup table was a value-based one.

When two lookup fields are placed on one line on a display, insert, or update form, the display might scroll. Therefore, the conversion will edit the following lookup fields on the standard Data Maintenance and Display form layouts that utilize them so that they will now display as wide rows.

-- Education: Degree (schldegree), Institution Name (schlinstnm), Concentration 1 (schlcon1), Concentration 2 (schlcon2), Concentration 3 (schlcon3), Concentration 4 (schlcon4)

-- Employment: Occupation (jobsoccup), Descriptor 1(jobsdescr1), Descriptor 2 (jobsdescr2), Descriptor 3 (jobsdescr3)

-- Chart of Accounts: CAE Description (table value from account_cae), Account Number (chart_acct)

If you have customized layouts of these display and maintenance forms, and you wish for these fields to display as wide rows, then you will need to edit your custom displays.

If you maintain other Lookup tables whose values are longer than 30 characters, then you will want to review the Display and Maintenance forms that utilize them in order to verify that their layouts are as you desire.

Millennium Hot Keys - insert/update form hot keys, 'v', 'i', and space bar - do not work in Firefox.

Update/Cancel button appears on the top left corner of a blank Millennium screen. Once these buttons appear, Millennium hangs and the IIS must be restarted.

Space Bar (Hot key for Next Search) does not take user to the Next Search Screen unless user makes the screen active by clicking somewhere on the screen.

A field to hold the IP Address of a constituent when he/she is a user logged on to the Online Constituent directory is added to corebio.

• coreuserip

The following new fields are added to support Millennium 78 enhancements

• user_mill_admin
• user_password4
• user_theme
• user_outlook
• user_we_import
• user_link_sort
• user_link_filter
• user_show_site_footer

user_sort is increased to 104 characters in length

user_filter is increased to 104 characters in length

The following new fields are added to support Millennium 78 enhancements

A new table is added to the database to support the Login Lockout enhancement.

The following fields are included in this new table.

• audit_key
• user_name
• IP_address
• login_date_time
• login_success

the actvstdium field has been added to the database to support the "Set the Type of Seating Layout on the Activity" enhancement.

tasks_type is a new lookup table that has been added to the database to support the Two Way Outlook Task and Calendar Synchronization enhancement. The table layout is the same as the Standard Lookup table layout save for the addition of its table_otlk field.

The following new fields are added to the tasks data table to support the Two Way Outlook Task and Calendar Synchronization enhancement

• tasktype
• taskremtim
• tasklocatn

The following new fields are added to the address data table to facilitate new CorrectAddress functionality due to new postal regulations.

• addrdpv
• addrnostat
• addrdpvcnt
• addrlacsch
• addrmovtyp
• addrcaupdt
• addrlacsdt
• addrccupdt
• addrcoamtc
• addrsupprs

A new table is added to support the Circles enhancement. Refer to the Circle Membership topic for its field listings

A new value-based, or super-lookup, table is added to support the Circles enhancement. Refer to the Circles topic for its field listings.

New lookup tables have been added to support the Circles enhancement. Their layouts conform to the Standard Lookup Table layout.

The following fields have been added to the gifts data table to support the new Pledge Transaction "Payment" Totals enhancement.

• giftttlpay
• giftcntpay
• giftttlcrd
• giftcntcrd
• giftttlwrt
• giftcntwrt

The following fields have been added to the dues data table to support the new Pledge Transaction "Payment" Totals enhancement.

• duesttlpay
• duescntpay
• duesttlcrd
• duescntcrd
• duesttlwrt
• duescntwrt

In the report_printers table, the length of the printer_path field is increased from 128 to 256 characters. The length of the printer_driver field is increased from30 to 256 characters.

In the report_options table, the length of the default_printer field is increased from 30 to 256 characters.

The link_file field has been added to the sorts system table to support the ability to define and use sorts on linked records.

The link_file field has been added to the filters system table to support the ability to define and use filters on linked records.

The length of the chart_cred and chart_debt fields are increased to 30 characters.

The length of the demovalue field is increased to 25 characters.

The ade_source lookup table is added to support the Advanced Data Examiner processing of pending data in data sets enhancement. The ADE Source fields that are added to the data tables reference this new table.

An ADE Source field has been added to each of the following data tables and their corresponding pending data tables to support the Advanced Data Examiner processing of pending data in data sets enhancement. . The ADE Source fields in each of the data tables references the ade_source lookup table.

New fields are added to support the changes that have been made to the Millennium User Interface.

To access several Favorites items and functions, a Millennium User has to be known to the system as a Prospect Management (PM) User. A PM User must also be a constituent on the database, and his or her User Id must be associated with his or her constituent Id number. In addition, a PM user must have one or more of the required Prospect Management Relationships as shown in the chart below.

The following chart details the required Relationships that are needed in order to be classified as a PM User - either Prospect Manager, Manager Assistant, Director, or Director Assistant

The Millennium Explorer, Favorites item expands to show Bookmarks, Prospects, and Recent Reports. If you are a Prospect Management (PM) User, then the Prospects item further expands to show My Staff, My Prospects, My Tasks, and Reassign. The My Staff and Reassign items are available only to Director and Director Assistant PM Users. The My Prospects item is available only to Prospect Manager and Manager Assistant PM Users.

Prior to this release, Bookmarks and Prospects were listed under the Millennium Explorer Profiles item. And, the Prospects item was visible even if you were not a Prospect Management User.

Users who are also database constituents have been able to, and still can, access Tasks by using the Millennium Explorer, My Millennium item. Now, each user who is also a Prospect Management User can access his or her Tasks by using the Millennium Explorer Favorites My Tasks item as well.

The My Prospects Favorites list display has been enhanced. For each constituent who is listed in the display, the system will, by default, show the Id Number, Formatted Name, the City, State, and Zip Code from the preferred Address (or first found, if no preferred Address exists), Type of Prospect Manager/Prospect relationship (the Whose side of the relationship), the Donor Tracking Capacity, and the Donor Tracking Last Research Date. Your site can choose to add fields to the display, remove fields from the display, and change the order in which the fields will display by using the My Prospects Display applet. Access this applet by using Millennium Explorer, Tools > Display Design > Display Options. Then, click on the Maintenance button located to the left of the My Prospects Display label.

Users can sort the display by clicking any one of the field names that are shown in the Table Header.

The display also includes a set of filters for users to use to refine the list to suit their needs. By default, My Prospects can be filtered by Address Region, Rating Campaign, Rating Cultivation, and Rating Inclination. Certain fields from the Actions, Address, Attribute, Basic Data, Custom Bio, Donor Tracking, Planned Gifts, Proposals, Rating, and Relation data tables are also available for use as filters. A System Administrator can use the My Prospects Filters applet to change what filters are available for this display, and can change the order in which the filters show. The My Prospects Filters applet can be used to add additional filters to the list, remove filters from the list, or change the order of display. Access this applet in the same way as the My Prospects Display applet - by using Millennium Explorer, Tools > Display Design > Display Options. Then, click on the Maintenance button located to the left of the My Prospects Filters label.

Finally, the display includes a count of the number of Prospects as well as a summary of the listed Prospects, by Rating Cultivation. The count and summary are dynamic. They will change as filters are applied and removed.

Each site will be able to maintain one My Prospects Favorites Display layout, and this is the only layout that is available for all of its users.

Access to the My Prospects Favorites list display is available to each user who is classified as a Prospect Manager or a Manager Assistant PM User (if necessary, see above for the definition of this).

If a user is not currently a Prospect Manager or a Manager Assistant PM User, then the My Prospects item will not be visible. When the user creates the first relationship with the required types, he or she must Log Off and then log back on to Millennium in order to view the My Prospects item.

A Prospect will show on a user's My Prospects Favorites list if the Prospect Manager/Prospect relation row is Active (the Relation Stop Date is either blank, null, or a date later than the current day's date). To access a prospect's data display, click on his or her Id number or Formatted Name. The data will be displayed in the user's One Screen Display format.

New codes and values are needed in the relationships lookup table for Secondary Prospect Manager (pms), Potential Prospect (pp), Prospect Manager Assistant (pmasst), and Prospect Manager Researcher (pmres). The conversion will add them if the codes do not already exist in the lookup table, and mark them as Active. And, all Prospect Management relationship types, including p for Prospect and pm for Prospect Manager, must remain marked as Active in order for this functionality to work as intended. If you have used other codes for Prospect and Prospect Manager, or if you have flagged the standard entries of p or pm as Inactive, this will need to be manually reconciled after the conversion. In addition, if you have used codes other than the standard codes for Potential Prospect and Secondary Prospect Manager, then you will want to flag your existing codes as Inactive and use these standard codes going forward.

The conversion will also add new and existing Prospect Management relationship types to the relation_pairs table. These entries are mandatory in order for this functionality to work as intended. (see below for the list)

New fields have been added to the sysinfo system table in order to store the names of the fields that are shown on the My Prospects Favorites display and the names of the fields that will be available for use as filters for the display.

See the System Display Options and Favorites topics.

A My Staff Favorites Display has been added. Access to the My Staff Favorites list display is available to each user who is classified as a Director or a Director Assistant PM User (if necessary, see above for the definitions of these). If a user is not currently a Director or a Director Assistant PM User, then the My Staff item will not be visible. When the user creates the first relationship with the required types, he or she must Log Off and then log back on to Millennium in order to view the My Staff item.

Each Director PM User will be able to access a list of the Managers they direct by using the My Staff Favorites item. Click the Id number or Formatted Name of any Manager to then access a list of that Manager's Prospects. This list will be formatted in the same way as the My Prospects Favorites layout is formatted for the site. Finally, click on the Id number or Formatted Name of a Prospect to access the Prospect's data. The data will be displayed in the user's One Screen Display format.

Each Director Assistant PM User will be able to use the My Staff Favorites item to access his or her Director's list of Managers, and from this list, the user can then access each Manager's prospects. In effect, the Director Assistant PM User is impersonating his or her Director.

A Prospect Manager or Secondary Prospect Manager will display on the user's My Staff Favorites list only if the Director/Manager (or Assistant/Director, or Researcher/Director) relationship is Active (the Stop Date is blank, Null, or a date later than the current day's date).

For each Manager who is listed in the My Staff Favorites display, the system will, by default, show the Id Number, Formatted Name, Employment Title, Type of Director/Manager relationship (the Whose side of the relationship), the preferred email address (or first found, if no preferred email address exists), and the Phone Number from the preferred Address (or from the first found Address, if no preferred one exists). Your site can choose to add fields to the display, remove fields from the display, and change the order in which the fields will display by using the My Staff Display applet. Access this applet by using Millennium Explorer, Tools > Display Design > Display Options. Then, click on the Maintenance button located to the left of the My Staff Display label.

Additional codes and values are needed in the relationships lookup table for Prospect Manager Director (pmdir) and Prospect Manager Secondary Director (pmsrd). The conversion will add them if the codes do not already exist in the lookup table, and mark them as Active. And, all Prospect Management relationship types must remain marked as Active in order for this functionality to work as intended. If you have used other codes for the values that are listed above, or if you have other entries that have been used for Director - type relationships in the past, this will need to be manually reconciled after the conversion.

The conversion has added new and existing Prospect Management relationship types to the relation_pairs table. These entries are mandatory in order for this functionality to work as intended. (see below for the list)

New fields have been added to the sysinfo system table in order to store the names of the fields that are shown on the My Staff Favorites display.

See the System Display Options and Favorites topics.

One Screen View functionality has been added to Millennium. One Screen Views allow a user to view the constituent and prospect data on a dashboard-like display. For more information about One Screen Views, see One Screen Data Display.

Circles functionality is added to Millennium. Circles offer a way to track relationships between a constituent and a group of constituents. For examples, Circles can be created and maintained for constituents who are members of the same family, work for the same company, or share a special interest.

Circles are considered to be a sub-World of Millennium. There are two components to the Circles sub-World - the Circle and the Circle Member. Defining a Circle involves giving the Circle a Name, a Code and a Circle Type. A Circle can be owned by a constituent, and several Circle display options can be set, including the option to display a Circle and all of its active members on a constituent's Relation Tree as well as an option to display a summary of Circle Member giving when displaying the Circle definition.

Once a Circle has been defined, constituents can then be assigned as members in the Circle. When a constituent is assigned, he or she can be given a position within the Circle, and the date that the member joined can be noted as well. A Circle membership can be updated at any time to set an End Date, thereby setting a member's status within the Circle to Inactive.

Data maintenance for each Circle is done by using Millennium Explorer, Profiles > Circles to access the Circle Search Form. The Circle Search form is then used to locate a Circle display. The Circle Search form is also used as the starting point for creating a new Circle.

All Circle Membership maintenance tasks for a particular Circle can be performed from the display of the Circle. This eliminates the need for the user to locate and display the data for each and every constituent who is or will be a Circle Member.

Information about an individual constituent's Circle Memberships can be viewed and maintained by locating the constituent and then use Millennium Explorer, Profiles > Biographical > Circle. Every Circle that the constituent is a member of will be shown as a separate data record in the display area. Each Circle Membership row can be updated or deleted from this display, and new Circle Membership rows can be created for the constituent from here as well.

The Relation Tree functionality is enhanced to include Circles. An individual constituent's Relation Tree display will a graphic representation of his or her Circle memberships. Nodes that represent every Circle (assuming that the Circle was flagged to display on Relation Trees when it was defined) that a constituent is an active member of will display on the Tree. From each Circle Node, a set of lines will branch to the names of the other constituents who are also active members of the Circle.

New tables have been added to support Circles functionality.

• circle_definition: This table holds data about the Circle. It is classified as a value-based, or super lookup, table, but has enhanced functionality.
• circles: This table holds data about Circle Members. It is a classic Millennium data table. Each row in it belongs to a constituent.

other lookup tables: The lookup tables listed here conform to the standard lookup layout and support standard and custom fields in the circle_definition lookup and circles data tables

• circle_position
• circle_type
• circle_def_lookup1
• circle_def_lookup2
• circle_def_lookup3
• circles_lookup1
• circles_lookup2
• circles_lookup3

Complete information about Circles can be found in the Circles and Circle Membership topics.

Constituent contact information - names, addresses, phone numbers, and email addresses - can be directly uploaded into the Contacts component of Microsoft Outlook. The upload is an on-demand process, initiated by each user. It can be initiated for a single constituent at a time, a user's bookmarked constituents, a user's prospects, or constituents that are listed in a worktable that is owned by a user's User Id. Once a user's 'targeted' constituents' contact information has been uploaded into Outlook, any updates to the information that are made in Millennium can be integrated with the information in Outlook at any time, for all contacts at one time, by using a Refresh command.

The system must be set to allow all users to upload constituent contact information to Outlook. This is done by selected the Allow Contact Upload check box on the System Options page.

Contact information can be uploaded from a constituent's data display by using the contact card icon located in the Constituent Info header display. Or, contact information can be uploaded for one or more constituents by using the various options on the Contact Upload form, accessed by using My Millennium > Contact Upload. Contact information in Outlook can be updated with Millennium changes by using the Refresh button that is located on this same page.

When contact information for a constituent is uploaded into Outlook for the first time, the process will create a new Contact item in Outlook. Even if a Contact item for a constituent was previously entered into Contacts by using Outlook, the process will still create a new Outlook Contact item. Millennium will never add to or overwrite the information for a Contact item that was originally created in Outlook, by Outlook.

If a constituent's Outlook Contact item was originally created by uploading from Millennium, subsequent uploads and refreshes will overwrite the Contact item with the data as it exists in Millennium at the time of the upload.

Millennium will not delete any Contact item from Outlook.

The Upload Contact Information to Outlook is a one way process, from Millennium to Outlook only. Any changes that are made to contact information by using Outlook will be overwritten when the next Millennium upload or refresh process occurs.

Firefox users - Tasks and Outlook integration will work for Firefox users who have installed the IE Tab extension.

A new field has been added to the sysinfo system table to support this enhancement:

• enable_contact_upload

Complete information can be found in the Upload Constituent Contact Information To Outlook topic.

The Millennium Tasks and Outlook Integration functionality is enhanced to:

1. Allow a site to decide if it wants to make Tasks and Outlook integration available to its users. If Outlook integration is made available, then a site can allow the integration to occur in real-time, or to allow the integration to occur only when the user wants it to.
2. Segment Tasks by Type: those that can integrate with Outlook Task items only, those that can integrate with Outlook Calendar items only, and those that cannot be integrated with Outlook at all.
3. Allow the user to decide if they want the integration to be a one-way or two-way process.
4. Allow the user to tell Millennium when to do the integration.
5. Allow the user to define rules that Millennium will use when performing the Tasks to Outlook integration.

The following conditions must be met before Millennium and Outlook integration can occur:

1. The system must be set to make integration available to all users. This is done by setting the Outlook Integration Level to Manual or Real-time, on the System Options page.
2. Individual Tasks must be flagged to allow them to be integrated with Outlook. This is done by using the Outlook Integration field in the tasks_type lookup table to flag a Task Type to integrate with either an Outlook calendar item or an Outlook Task item.
3. The user must be a Millennium constituent. And, his or her User Id must be linked to a constituent Id number.
4. The user himself or herself must allow integration to occur. This is done by setting the Enable Integration Option on the User Options page.
5. The user must be running Outlook version 2003 or later.

Firefox users - Tasks and Outlook integration will work for Firefox users who have installed the IE Tab extension.

The tasks_type table is a new lookup table added to Millennium to support this functionality. It has the same layout as the standard lookup table layout save for one additional field - tableotlk. This field acts as a flag to inform the system that any Task assigned this Task Type is available for either Outlook Tasks or Outlook Calendar integration if other conditions are met, or that a Task assigned this Task Type is not available for Outlook integration. A Millennium Task can integrate with an Outlook Task item or an Outlook Calendar item, but not with both. This is a change from the previous functionality.

The Millennium 78 conversion process will populate the Tasks Type table with the same codes and values that already exist in the Actions Type lookup table, and the value of the tableotlk field will be set to N (not available for Outlook integration) for all entries.

New standard fields have been added to the tasks data table to support this functionality. They are Task Type (tasktype),Task Location (tasklocatn) and Reminder Time ( taskremtim). The Task Type field is 'driven' by the tasks_type lookup table. When creating a Task that links to an Action, the values of Task Type and Task Location will default to the values in the Action Type and Action Location fields. If the Action Type value does not have an equivalent active entry in the Tasks Type lookup table, then the value of the Task Type will default to the first active code in the Tasks Type code. These defaults can be changed before the Task record in inserted.

If you have customized the layout of your Tasks display and maintenance forms, you must edit the custom displays to add these new fields.

New code/value entries are required in the priority lookup table in order to take advantage of Outlook's Priority field. These entries are as follows:

New code/value entries are required in the task_status lookup table in order to take advantage of Outlook's Status field. These entries are as follows:

The conversion will add the required codes and values to the priority and task_status lookup tables only if the codes do not already exist. If a required code is already in the table with a different value it will not be changed. The values of these entries may duplicate the values of previously required entries in the lookup tables. The previously required entries had different required codes. For example, a status of In Progress had a required code of inprog and it now has a required code of 1. After running the conversion, sites who will use Outlook Integration will mark the duplicate old entries as Inactive, and use the new code/value entries going forward. Sites who do not plan to use Outlook Integration will mark the duplicate new entries as Inactive instead.

A new field has been added to the sysinfo system table to support this enhancement:

• outlook_integration

A new field has been added to the userlist system table to support this enhancement:

• user_outlook

Complete information can be found in the Tasks with Outlook Integration topic.

To support the new My Prospects and My Staff functionality, new code/value entries are required in the relationships lookup table

New relisa/ relwhose entries are also required in the relation_pairs lookup table

A Show/Hide Payments menu item is added to the menu that is accessed by pointing to the Gift or Dues section header Edit button.

When the option to Show Payments or Hide Payments is set by using the Edit button located to the left of any Pledge Transaction that has linked payments, credits and/or write-off transactions, the display will return to particular Pledge Transaction from which the option was selected

The system will calculate counts and totals for all payment, bequest, credit, and write-off transactions that link to a Pledge transaction through the giftplgkey/duesplgkey. Pledge transactions are those transactions with a type of pledge, expectancy, sustainer pledge, match pledge, pledge potential, or pledge credit. These totals and counts will be stored in separate fields in the Gifts and Dues data tables and will be available for display and for reporting purposes. When a user sets the Show/Hide Payments giving (or dues) display option to Hide, the counts and totals that display on the summary line are pulled from these fields.

Only pledge payments, bequests, credits, and write-offs that link to a Pledge through the giftplgkey/duesplgkey will be included in the totals and counts. Other transactions that link to the payment, credit, or write-off transaction (such as honors, memorials, and other credits) will not be included in the totals and counts.

On multi-allocation Pledge transactions, the totals and counts will be per allocation.

When a payment/bequest, credit, or write-off is linked to a Pledge, the relevant total and count will increase. When a payment/bequest, credit, or write-off is journaled or deleted, the relevant total and count will be reduced.

The following fields have been added to the gifts and the dues data tables to store these counts and totals. For non-pledge transactions, the values for these fields will be set to 0.

See the Giving Detail and Dues Detail topics.

The Gifts and Dues Default Insert Forms now include the Joint With, Credit For, Honor/Memory For, Special, and Solicitor Check boxes that are currently on the Main Insert forms for Gifts and for Dues.

The rules that are followed for setting the Joint, Credit, Honor/Memory, Special and Solicitor options are the same as the rules that are followed when using the Main insert form during data entry. These are: the user can not check both Joint With Spouse and Joint with Other, the user can not check both Joint With Spouse and Credit For Spouse, and the user can not check both Default Solicitor and Other Solicitor check boxes.

During data entry, the Default Insert form check box settings can be overridden before the data record is inserted.

Update/Archive functionality is added for Employment. If your site makes it a policy to retain the details of previous Employment rows by creating a new row instead of updating an existing one when a constituent's job information changes, then the Update/Archive feature will facilitate this process. When Update/Archive is used, the system automatically edits the existing row by setting the Status to No Longer at this Position and the Stop Date is given a value in accordance with a specified set of rules. The system then prompts for the creation of a new Employment row for the new information.

See the Employment topic for complete details.

Sorting and Filtering can be applied to linked data rows when they display with the primary data row to which they link. These Sorts/Filters are independent of any Sorts/Filters that are defined and used when rows from the same data table (as the linked data rows) are viewed from a constituent's display of that data table. For example, a Sort that is defined and applied to Attribute rows that link to Basic Data rows can not be applied to Attributes when they are displayed from a constituent's Attribute Data display. These Sorts/Filters are also independent of any Sorts/Filters that can defined and used when rows from the same data table (as the linked data rows) are linked to a primary data row from a different table. For example, a Sort that is defined and applied to the Attribute rows that link to Basic Data rows can not be applied to Attribute rows that are linked to and display with a constituent's Education row.

Sorting and Filtering is available for only for the following linked data rows.

Attribute rows that link to Basic Data, Donor Tracking, Education and Employment

Relation rows that link to Donor Tracking, Planned Gifts, Proposals

Actions rows that link to Planned Gifts, Proposals, Tasks

Task rows that link to Actions

On the 'Link to Existing' feature, when you select a Task and you want to link it to an existing Action, it assumes an Action for the same Id as the Task Id. Typically, the Action Id is the prospect, and the Task Id is the prospect manager. For the Task/Action linking, we should have the ability to search for the Action Id we want to link it to. The Task linking features should have a Link to Other Action feature.

When you link any record to other, the search screen displays a message:

'No match on criteria. Must respecify or Cancel'.

This message displays before you enter any criteria.

On the Snapshot screen, you can activate the flyover and select Options>Define filter/sort. Once you create the filter/sort, it is applied to the primary data screen, but not the snapshot. Remove the option to define filter/sort from the snapshot screen flyovers.

When inserting Securities information via default, you cannot cancel out of the form.

When you try to insert an Action linked to a Proposal or Planned Gift, you get a screen with just the table name and the insert and cancel buttons, no insert form is presented.

Last Search does not work after linking records or inserting record that requires a constituent search, like a relationship or a gift credit.

When no results are returned on a search query, you cannot clear superlookup fields to respecify. The field will clear, but the search is sent using the cleared criteria. The fields will repopulate when 'No Match' returned.

If a Search Results screen displays, the Next Search and Last Search Millennium Explorer items are not available. To return to a Search Millennium Database form,click on the refine the query hyperlink, or the Return to the Search Screen hyperlink if that is the hyperlink that is available instead. If you use the refine the query hyperlink, the Search form will be populated with information that you used in the previous search. A blank Search form will display If you used the Return to Search Screen hyperlink instead.

If a line from the Phone table is added to Copy to Clipboard, only the first Phone row and Internet Address row display - others are hidden.

On a Match Pledge Transaction, gifts are not displayed after adding 'Credit for this constituent' from the transaction menu.

When a new sort is created, it is not automatically set to active, this is different from the behavior of a filter or prototype which when created is set to active.

Performing a Journal & Correct transaction on a gift followed by a simple journal transaction; removes the transaction from Long and Short display. This transaction will only appear when set to Mini display.

Report criteria including any column from the bookmark table produce queue history error: A view does not exist for table #99.

When linking an action to a proposal, the actions form layout is missing. Only the Insert and Cancel buttons appear.

When the propacctcf system column is added to the proposal form layout, the system does not display the Account CAE code/value associated with the chosen chart of accounts lookup.

After modifying either the relisa or relwhose value of a linked tracking relationship row, the reciprocal relationship drop down menu is empty.

The Prospect Financial (finamount) field accepts only 8 characters if customized to display as a wide row.

When you enter in an Actions Tasks comment that extends past the first line of display, an extra blank line is being displayed in the comment.

When you are on a Corporation record and you click on an employee address hyperlink, their address contains links to all the Corporation's linked employee addresses. It should only contain the link address of the Corporation.

Actcompflg is not updated when the Actcompdat is entered in Oracle from the tasks being all set as complete- this is an issue as the standard Tasks Report is dependent on this flag to determine pending Tasks.

Cannot filter on the 'giftacctno' gift account number when inserting the initial filter row.

Performing an advanced search that returns more than 500 records prompts the user with: The maximum display number of 500 names has been reached. Use the Next button at the bottom of the Search Results page to display additional names. When the user selects the Next button the following error is generated:

When a constituent has multiple Internet Addresses and the Copy to Clipboard Columns has been used to include any of the Names Columns, causes the constituents multiple Phone Numbers and Internet Addresses to not be displayed.

When an Alert has been created and the body of the message utilizes a carriage return, it causes the Alert to not get fired off and an 'Error on Page' when the user attempts to delete a record.

When viewing the Prospect Tree, you receive an ORA-01858: a non-numeric character was found where a numeric was expected. Display Failed: Couldn't open data source error.

When entering in a giving transaction paid by credit card, you are unable to insert the credit card transaction without using a valid credit card number.

The Giving Trends graph is displaying in calendar year instead of the fiscal year.

When inserting a new Proposals record, you receive an error message that the Years field requires a 4 digit year.

When entering in a joint with spouse gift transaction, the gift deductible 'giftdeduct' and non-deductible 'giftnonded' amounts are not evenly split on the records when a gift transaction is created with an 80\20 quid.

Giving Tree Totals do not display an equally between spouses for a 'Credit for Spouse' pledge transaction with multiple payments and write-off.

Posting an overpayment to a pledge allocation and then journaling the payment leaves the overpaid amount in the payment schedule.

Legacy User Specific Fiscal Year setup causes bad data display.

Guest record not created if preferred address zip code is bad.

If an Activity is entered without a name, there is no way to access the Activity from the interface to update or delete it, as the link to access it is based on the name only.

The Millennium technology update and the removal of the Windows client from the software made it necessary to re-write the Seating Layout application. It is now in the form of an applet. After you have chosen the Event and Activity, access the Seating Assignment applet by using Millennium Explorer, Events>Seating.

The Guests Attended (Guestattnd) system column does not automatically update to 'No' when all guest attendance activities (Attattnded) are updated to 'No'.

A partial value search on any combination of characters after the first 30 characters of the event name does not return the event to the search results.

The User Options settings pages can be accessed by using the Millennium Explorer, My Millennium> User Options in addition to using Millennium Explorer, Profiles > User Options.

Agent Server.exe and its personification as an animated character (for example, Merlin) have been removed. The Agent is now known as the Millennium Assignment Service. Through Assignments, the Millennium Assignment Service can be set to notify users by email when Advisories have been posted. Posted Advisories can continue to be viewed from the Advisories display accessed by using My Millennium > Advisories > View.

Access the Notification Check Interval option by using Millennium Explorer, My Millennium>Advisories>Options.

The Agent Server must be removed from all machines before upgrading to Millennium 7.8.

Solicitor Assignments are failing. Error in millsvc.log:

When inserting a task with a long subject line from the My Millennium Tasks page, the column headers do not keep their spacing.

Selecting Chart Display on Campaign Totals in My Millennium causes the rest of the Home Page to disappear, you have to click back on the Millennium world to get back to the home page, where the Campaign Total display returns to the Graph.

When you let the cursor hover on the title (Campaign Totals) and select Include Pledges, the screen changes so that My Advisories and My Tasks disappear and Campaign Totals is at the top of the page with no chart display.

If the chart is accessed from My Millennium, Charts and Graphs, Campaign Totals, it functions correctly, the problem occurs when it is added to the Home Page.

The option to run a report to the "Print Preview" destination is no longer an option that is available through the Crystal run time. Therefore, this option has also been removed from Millennium.

To preview a report, set the report destination to either HTML or PDF and then access the report by using the View Report Millennium Explorer item.

On the Express Reports form, the Destination list box, Printer Choice list box, Print Criteria check box, Export Type list box and Export File Name text box have been moved from the Options tab to the Format Tab. The Destination list box label has been changed to Output.

Users can continue to use the keyboard to navigate the controls on the Query and Totals FasTabs even if the criteria statements on the tabs include value-based lookup fields. Prior to this release, if a value based lookup was defined as part of an Express Report, and the super-lookup Search applet was activated, the focus was not on any button. The user had to click the Search button to activate search process.

Millennium 7.8 is delivered with Qlikview 8.5. If you currently have Qlikview version 8.2, it will be uninstalled before 8.5 is installed. And, during the 8.5 installation, your server configuration will be reset to the default. After installation, you must re-do the Visual Analyzer configuration. VisualAnalyzerSetup.doc has complete details. This document is located on the Millennium 7.8 installation DVD.

Millcrypt_crystal.dll has been replaced by CRUFL_mil.dll. CRUFL_mill.dll is a .net assembly that is loaded in the Global Assembly Cache by the Millennium Reporting Server installation. Also provided is the CRUF_mil.tlb file that is used by some languages when developing using the .net assembly (for example, VB6).

A standalone installation program exists at the root of the Millennium installation DVD, if you need to install CRUFL_mil.dll on a machine that does not have a Reporting Queue, such as a Report Developer's machine. The name of this installation program is crystal_crufl_mill_install.exe, and it installs CRUFL_mil.dll in the Global Assembly Cache of that machine and an additional file - CRUFL_mil.tlb - into Program Files\Common\Millennium\Crystal UFL directory.

Add browse button to Import file applet to allow users to browse to files on their local drives.

When creating new report criteria, the operator drop down menu does not respond on first click when you try to select a value from the menu

When you click on the Visual Analyzer reports in Firefox, you are prompted to open or save millmoon.dll.

Campaign Results>When you export the Campaign Trends chart to Excel, the count of donors is formatted as a monetary field.

qlikview applet bug:

Objects which have been set to not allow moving or resizing in QlikView Enterprise are able to be both moved and resized when they have been minimized manually or automatically in the QlikView Java applet. These objects cannot be moved or resized in the page when viewed in QlikView Enterprise.

When creating report criteria using the correspondence table, the field corrid is labeled 'Const. Name' instead of 'ID' in the drop down.

When running reports in Millennium, links between primary tables and custom lookup tables are ignored. As a result fields from the custom lookup tables are not populated in the final output.

Prompted replies are not saved correctly when using Totals.

When you pass the standard total_title parameters to a Crystal format, the report will fail with error.

Reports hang in 'Crystal' stage when running Queue as a service.

If the 'not applicable to this report' check box was selected in a previous run of a report using the 'between' operator on prompts, on subsequent runs the second value of the prompt contains the text '<a prompted reply>'.

Report criteria including any column from the bookmark table produce queue history error: A view does not exist for table #99.

When creating or editing report criteria, the criteria screen does not load and you will receive a java.lang.NullPointerException error in the Sun Java Console.

Edit criteria screen not loading in Internet Explorer. The report title will display at the top of the screen. The java coffee cup will display beneath the title, but the rest of the edit criteria screen never loads. In the bottom of the browser window it says 'Loading Java applet'.

This is only happening in Internet Explorer.

When running a report that uses the Employment Occupation field, the 'not applicable to this report' check box is not available on the prompts screen when used with groups.

When creating a report or running an existing one with a criteria on coreprefyr using an operator of between and a prompt, then zero records are selected at run time.

Reports using between prompts with any year field does not populate the 2nd datetime prompt after clicking the second button to enter a date from the calendar control.

After lines of report criteria are cut out to the clipboard, the paste item in the action menu bar is not available to reinsert the criteria.

Long comments (corrcomm) truncated when using the correspondence utility.

When running a report to the Preview destination, you receive a 'Crystal Print Engine could not be opened' error. (This option had to be removed from Reporting. The Print Preview destination is no longer an option that is available through Crystal Run Time.)

Editing scheduled export reports changes the destination to HTML and if the destination is set back to export the OK and Delete buttons are disabled.

When you turn off the 'Use Calendar' option for an object, the calendar continues to display when entering in the prompted value at runtime.

After running the Summaries and Years utilities, a stranded qqq file remains in the queue folder causing the Queue to try to rerun the utility repeatedly in error.

When creating a report and you add a saved total to the report, you receive a Windows Clipboard Paste error message that the maximum number of lines, 2000, has been reached.

Running report criteria using the between operator with prompts for any date field is not properly converting prompted date values for the select statement to select the correct records.

Users can access Microsoft MapPoint™ software by using Millennium Explorer, Reporting > Maps. To create a new map, users select New Map. After selecting the worktable to use as the basis for the map, Millennium will launch MapPoint™in a separate browser window. Once launched, MapPoint™ will be in control, and Millennium cannot regain control until the user exits the MapPoint™software.

Users can view or edit an existing map by using Millennium Explorer, Reporting > Maps > View Map.

Maps can not be deleted from within the Millennium application. You must use Microsoft Windows Explorer, or the equivalent operating system navigation tool, to delete existing Map files.

See the Maps topic.

Microsoft MapPoint™ 2009 is authorized for use with Millennium. Previous versions of MapPoint™ will not be supported.

A donor who makes a gift to your institution by using the Online Constituent Directory now has the option to make a Pledge donation. The donor will supply the pledge amount, the due date for the first payment, the type of Pledge (annual, monthly, and so forth), and the number of payments that he/she will make to fulfill the pledge commitment. The donor has the option to tender the pledge by Credit Card or Bank Draft. Or, the donor can instruct the site to bill him/her later by picking the Bill Me Later payment option. When the donor submits the Pledge, if the chosen tender is Credit Card or Bank Draft, the Credit Card/Bank Draft information supplied by the donor will be stored by Paya Payment Solutions (SPS), but his or her credit card will not be charged (or bank account funds withdrawn) at this time.

When the Pledge is processed through the Advanced Data Examiner, Millennium will use the information from the Pledge Amount, Pledge Date, Pledge Type, and Payment Count fields to create the Pledge and a Pledge Payment Schedule. If the donor chose a tender of Credit Card or Bank Draft, then Millennium will link a Credit Card row to the Pledge transaction to hold the information needed to retrieve the credit card or bank account information that is stored in Paya Payment Solutions.

When the SPS Pledge Processing Tool selects the Pledge for processing, Millennium will then create a pledge payment transaction and a Credit Card row that links to the payment. It is only when the Processing Tool selects the Pledge for processing that the donor’s credit card will be charged, or funds will be withdrawn from his/her bank account.

When you click cancel on the credit card screen from Donate Now for non-constituents from OCD, it sends you back to the logon screen, not the previous screen where you entered donation information. It should go back to the previous screen.

Java no longer needs to be installed on the workstations that constituents and non-constituents use to access the OCD. This allows access by any browser to the Online Constituent Directory and in particular, the Donate Now forms.

Search Results table not being deleted from database when user exits the browser session instead of logging out of the Online Directory.

When loading the OCD logon screen, the cursor does not focus on the User Id field when using the latest Sun Java build.

When entering in a donation paid by credit card in the Online Constituent Directory, the payment is declined because the credit card expiration month and year are reversed when processed in Paya Payment Solutions.

The Online Constituent Directory allows users to login with invalid User Id and passwords creating a security risk where the user could potentially have access to restricted data in the database.

When clicking the 'Did you forget your User Id or password?' link to request your OCD User Id and password be sent to you, you receive a &rdquor;Field can only contain letters, numbers and '/'” message when entering in a valid email address.

If you enter your email address in an online donation in the OCD and then request your User Id and password, you receive a 'Constituent not found in system' error.

hyperlink embedded in an email to direct an OCD constituent directly to the Donate Now form does not work.

When submitting Online Credit Card donations within OCD Donate Now using a Mac, the transactions do not pass to the Data Examiner or SPS.

An input file field that has a date format can be mapped to the day that the import file is imported into the pending tables.

See the ADE Import Tool topic.

Several changes have been made to the ADE Import Tool's user interface.

On the utility's main window, the Browse to Log File controls have been relocated. They are directly below the Browse for Input File controls.

On the main Mapping window, the options to create a data row by Id Only, by Id and Type Only, and the option to Match an input file row to an existing Millennium data row have been removed from the mapping window's menu bar and have been placed on the tab for each individual table.

All Extra Pending Rows windows will display the tabs for all of the extra pending rows that can possibly be mapped at one time. Prior to this change, the Extra Pending Rows windows loaded only with the tabs that corresponded to the number of extra pending rows that had already been mapped. If no extra rows had been mapped, then the windows loaded with only one tab. The Map Another <table name> Pending Record menu item has been removed from the File menu on all of thte Extra Pending Rows windows. Now, A user clicks on a tab to map the fields for the next extra pending row. The Remove the Mapping Plan Settings/Options menu has also been removed from the Extra Pending Rows menu bars. The functionality of the Create a new <table name> row if only Id and Type Have Data menu item, and the functionality of the Check for Matching <table name> by Type menu item is now accessed on each of the individual tabs.

Save and Close buttons have been added to the Main Mapping window. Close buttons have been added to each of the Extra Pending Rows windows and to each of the Event-related mapping windows.

On the Main Mapping window, the Map/Change Other Event Table Rows menu is removed. To access the Event Guest and Event Income mapping windows, click on the Registration table tab, and use the Action check boxes that are located there.

On the Event Guest mapping window, the Map/Change Activity Attendance Row and Map/Change Event Item Row menus have been removed from the File menu. To access the Activity Attendance and Event Item mapping windows, use the Action check boxes that are located on each of the Event Guest tabs.

On the Activity Attendance mapping window, the Map/Change Activity Item Row item has been removed from the File menu. To access the Activity Item mapping window, use the Action check boxes that are located on each of the Activity Attendance tabs.

Set the ADE Import Tool topic.

The Advanced Data Examiner can be set up so that when it processes new constituents, it will attempt to match them to existing Millennium constituents (this is functionality that exists prior to this release). By default, the system will display the Id Number, Formatted Name, Line 1, City, State and Zip Code from the preferred Address, Constituent Type, and Preferred Year for each constituent who meets the ADE Matching Level Criteria. Your site can choose to add fields to the display, remove fields from the display, and change the order in which the fields will display by using the ADE Search Results Applet. Access this applet by using Millennium Explorer, Tools > Display Design > Display options. Then, click on the Maintenance button located to the left of the ADE Search Results Display label.

New fields have been added to the sysinfo system table to support this functionality.

See the System Display Options and Advanced Data Examiner topics.

The Advanced Data Examiner can process data in the pending tables all at one time, or in data sets.

The ADE Source (ade_source) lookup table is added to the database to support this functionality. It conforms to the standard lookup table layout, with the following exceptions - it does not have a table_code field, and the table_val field is 30 characters in length. "Soft Edit" and "Online Directory" are required table entries. The conversion will insert these entries, and a <blank>, and mark them as Active.

An ADE Source field is added to each pending table and each pending table's corresponding data table. These fields reference the table_val field of the ade_source lookup table. Only the Advanced Data Examiner can populate these fields in the data tables, so they will not be available on any Data Maintenance forms.

Millennium will automatically assign a source of Online Directory to pending data rows that are created by Online Constituent Directory users. It will automatically assign a source of Soft Edit to the pending data rows that are created because of the data maintenance tasks performed by soft edit users. When the ADE Import Tool imports rows into the pending tables, the rows can be assigned any source, other than Online Directory or Soft Edit, as long as that source corresponds to an active entry in the ADE Source lookup table. If no source is assigned, then the ADE Source field for all of the imported pending data rows will be blank.

When the Advanced Data Examiner is used to review data in the pending tables, the user can instruct the ADE to load all of the data in the pending tables for processing, or to load only a segment (set) of the data by choosing a specific source from the Import Source drop list box that is located on the Data Summary page. Whether the ADE inserts new rows into the data tables, or updates existing data table rows, the import source that is assigned to the pending rows will be stored in the data table rows. It is therefore possible that the original ADE source assigned to a data row will be overwritten.

See the Advanced Data Examiner and ADE Import Tool topics.

After inserting/updating an Events ADE default, the navigation menu disappears.

Soft Edit Users updates to relation row not written to relation_pending tables.

Gift transactions that have a tender type of Credit Card are not being not written to the Credit Card Table if they have been imported utilizing Data Examiner.

When manually updating a new constituent in the Data Examiner using IE 7, you receive a HTTP 400, 'The webpage cannot be found', error when the record contains a '#' in the address.

Automatically updating imported records when new constituent Matching Levels have been selected generates duplicate Name and Address rows on an existing constituent record for the 'sa' and 'MILLORA' users.

When accepting a New Constituent pending record for an OCD non-constituent donation that was entered with an ampersand in the name, you receive an Internet Explorer, 'HTTP 400 - The web page cannot be found' error message.

Deleting a record in Manual Update\Archive does not allow the user the option to 'Archive' additional pending address records.

When an Address is automatically updated using the Data Examiner, the Address Start and Stop dates are not being updated on the address record.

When you setup an ADE Define Default on the Gift table with an Effective date, the Effective date on the Manual update screen is being populated with today's date instead of the Effective date from the defined default.

All calendar buttons used in the Data Examiner Defined Defaults are not functioning properly.

Mapping custom lookup fields to a code in your csv file generates an error when running the import. If you try to map the field to a specific lookup value in the ADE tool, the table values are not retrieved and displayed in the applet window.

When manually updating relationship pending records in the Data Examiner, you receive an Error Code 30003 'relrelatid cannot be blank' error.

Manually Updating a new constituent in the Data Examiner is generating a white screen when ADE attempts to match a potential new constituent (Corporation) to an existing constituent in Millennium whose matching levels are set to Last name / first Initial and there is no value in the First name field.

Any Millennium database user can be given most System Administrator rights and permissions. A user who is given Millennium System Administrator rights and permissions is called a Millennium System Administrator, and is distinguished from the Database System Administrator. The database administrator is the user who logs on to Millennium with the sa/MILLORA User Id.

The purpose of this enhancement is to allow a user, other than the Database System Administrator. to perform Millennium System functions such as adding new users, setting system-wide options, creating system-wide Sorts and Filters, and customizing display and maintenance forms. Millennium System Administrators will not have permission to run Millennium upgrades (convXX.exe), and other system utilities including create.exe, orclpkg.exe,prototype.exe, Public Synonyms.exe, and sequence.exe. In addition, the View Generator will not be available to Oracle Millennium System Administrators.

Millennium System Administrator rights and permissions are granted for the Millennium database only.

We strongly advise sites to not assign Millennium System Administrator rights and permissions to an existing user. Instead, create new credentials (User Id and password) for the user. The user should use these new credentials when logging on to perform System Administrator functions, and use his or her other user credentials when accessing Millennium for any other purpose.

If an existing user is updated to be a Millennium System Administrator, all Sorts and Filters that were defined when the user was a regular user will no longer be available for him or her to use and maintain. They will be available again when the user's System Administrator privileges are removed.

If an existing user is updated to be a Millennium System Administrator, and the user owns tables in the millreports database, you will need to transfer ownership of those tables to another user first. Going forward, report criteria that is saved by a Millennium System Administrator will not be owned by 'dbo' and not by the User. However, worktables that are saved by a Millennium System Administrator will be owned by that Millennium System Administrator.

A new field is added to the userlist system table to support this new functionality:

• user_mill_admin

The database administrator is automatically a Millennium System Administrator as well. Therefore, the conversion will set the user_mill_admin flag to 1 for the Database System Administrator.

A new setting security setting has been added to allow users in import data from Wealth Engine into constituent records. For more information, see WealthEngine.

An Add Row button is added to the bottom of the Custom Display Designer. Users have the option of clicking the Add Row Navigation Menu Bar item or clicking the Add Row button when they want to add a row to a data display or maintenance form.

An option has been added to allow you to customize your One Screen View using the Custom Display Designer.

Existing system-wide settings that pertain to the way that Millennium is displayed to all users have been moved from the System Options page to a new page called System Display Options. This new System Display Options page is accessed by using Millennium Explorer, Tools > Display Design > Display Options. These settings are:

• Default Screen Resolution
• Spouse Button Label
• Social Security Display Mask
• Credit Card Display Mask
• Bank Account Display Mask
• Search Results Display

To support Millennium 78 enhancements, additional system-wide settings have been added to the System Display Options page. These settings are:

• Prospect Count Label
• ADE Search Results Display
• My Staff Display
• My Prospects Display
• My Prospects Filters

To support Millennium 78 enhancements, the following system-wide settings have been added to the System Options page. These settings are:

• Audit user login attempts
• Number of login failure before user lockout
• Duration of lockout minutes
• Advisory Notification Return eMail Address
• Task Integration with Outlook
• Allow Contacts to be Uploaded to Outlook
• Auditing
• WealthEngine

An ODBC connection to the millreports database is no longer necessary. To successfully execute Printers.exe, you must have an ODBC connection to the data database.

Printer names must be no more than 90 characters long.

The size of the application's window has been changed to account for the increased length in the printer driver name and printer location.

Labels have been edited to add clarity to what is being displayed on the application's window.

Database Administration tools must be used to change the password for the Database System Administrator. This is the user who logs on to Millennium with a sa/MILLORA User Id.

The Database Administrator password can no longer be changed by using the Millennium interface. The Password and Confirm Password text boxes have been removed from the User Maintenance form for the sa/MILLORA user. A message to inform the user that the sa/MILLORA password may not be modified from within Millennium has been added to the form instead.

The Lucinda Console font name entry is changed to Lucida Console. The Lucinda Sans Unicode entry is changed to Lucida Sans Unicode.

You must be either the Database Administrator (sa or MILLORA User Id) or a Millennium System Administrator in order to execute the following standard utilities.

• Area Code Update
• Assign Summary Definitions
• Set Years Parameters
• Generic Import
• Gift Import
• Harris
• Phonathon
• Printers
• Zip Code Address Update
• Zip Code Table Update

A confirmation box will not be displayed when removing a Reporting Queue, OLAP Server, Replicated Database or Reporting Printer from System Information Settings.

You must specify a date range when processing sustainer pledge payments. The date range that you specify must limit the sustainer payments that are selected to the current month in which they are due. If you do not specify this date range, then the Pledge/Sustainer Payment Processing tool may create and process more payments than what are actually due.

If you do not run the Pledge/Sustainer Pledge Processing tool for the month that a payment on a sustainer pledge is due, then you can manually post the payment from the constituent's Giving (or Dues) display. Once posted, the credit card or bank draft transaction will automatically be processed if Real Time processing is available for your User Id. Or, the credit card/bank draft transaction can be processed by using Batch Payment Processing.

When the coressnum is not populated in an existing corebio record and the SSN field is not populated in the input file, the coressnum is updated anyway and displays non-numeric and other ASCII characters (why - a blank is decrypted, and then encrypted)

Getting error when attempting to insert new comment_type. Error references non-existent 'commowner' column.

User maintenance should use giftcruser and gifttrnum instead of giftuserid and gifttrnum to identify user/transaction number combinations.

When making an online donation, if submission to SPS fails, Millennium tries to insert a record into the table account_services_log. The insert statement throws an 'unclosed quotation' error.

When you insert a new SPS merchant account, it is not available for online donations until the IIS is reset.

In Lookup Maintenance, searching for any value with a single quote throws a SQL error similar to:

MillInet: Couldn't open data source. Please contact the system administrator.

Incorrect syntax near 's'. Unclosed quotation mark after the character string ') ORDER BY UPPER(table_val)'. Statement(s) could not be prepared.

You get a similar error on an insert, depending on the length of the value. The entry will be added to the database even if you get the error. When you try to update the entry, the flyover menu sometimes will not activate for that entry. This happens with batches.

On the Solicitation search form in lookup maintenance, wildcard search ('%') does not return all solicitations. If sol_accnt is NULL, the entry is not returned.

In datasync, the lookup value search window has a button in the lower right hand corner that is cut off. The button functions when you click on it, but it is mostly cut off on the screen.

When performing maintenance on superlookup entries, if you change the value of one of the entries, the record is not displayed following update.

Formatting is removed from comment fields in all tables even if Remove Formatting in Comments: is set = No

Also, Formatting is misspelled on the System Options page.

SPS log shows payment made after credit card rejected.

When merging two Corporations the total number of known employees is getting doubled.

When deleting a user in User Maintenance, you receive a 'Drop User -00000' database error.

The Default Queue and Default Printer settings for users are being overridden by the Group settings when these settings are not set at the Group level.

When a pledge credit card payment is processed through SPS, the payment is being displayed on the spouse's record instead of the primary constituent's record.

Millennium Help has been given a new, updated appearance for this release. Links to related topics are moved from the bottom of each topic page to the topic page header. Several improvements have been made in order to aid users when searching within the Millennium Help files. The topic titles for most of the Help files have been updated to better reflect the topic's content. And, the topic titles as they are listed in Search Results will closely match the title on the topic page. Search results on the Help topic pages are now highlighted in yellow. Users no longer have to scroll through an entire topic to locate the content relevant to their search.

The name of the field in the pendingid table is pendingid, not autoid, as previously documented.

The sysinfo table description is moved to its own topic page: sysinfo.

The Internet Links topic has been removed from the Help Files. All of the links that were accessed by using this topic page can be accessed by using Millennium Explorer, Reference > Other Links > Research Links.

Information about Browser specifications and settings maintained in the Help files are also maintained in several Millennium Installation and Set Up documents that are available on the Installation DVD. Information about Browser specifications and settings has been removed from this page, and the user is instructed to refer to the Installation and Set Up documents for the information instead

The following was added to the Pledge/Sustainer Pledge Processing Tool documentation:

You must specify a date range when processing sustainer pledge payments. The date range that you specify must limit the sustainer payments selected for to the current month in which they are due. If you do not specify this date range, then the Pledge/Sustainer Payment Processing tool may create and process more payments than what is due.

EXAMPLE Create a sustainer pledge on February 1, 2010, with payments due on the first day of every month of the year. The first payment is due on March 1, 2010. If you run the Pledge/Sustainer Payment Processing tool on March 1, 2010 and you do not specify a date range of March 1, 2010 through March 31, 2010, then the tool will create and process the payment that is due on March 1, 2010. The next month you run the tool without dates specified then the tool will create a payment for April 1, 2010, plus the payment for the payment that was due the previous month, March 1, 2010. The following month there would be 3 payments, and so forth.

If you did not run the Pledge/Sustainer Pledge Processing tool for the month that a payment on a sustainer pledge was due, then you can manually post the payment from the constituent's Giving (or Dues) display (see the Pledge Payments topic). Once posted, the credit card or bank draft transaction will automatically be processed if Real Time processing is available for your User Id. Or, the credit card/bank draft transaction can be processed by using Batch Payment Processing.

Clarified documentation for the following issue: When using stored parameters, if the column 'lookup_table' is populated with a table name, no values are available for selection at the prompt. If the column is populated with a column_name, values are available.

Help-Bad link on Qlikview refresh utility page.

The Millennium documentation does not indicate that using the 'equal to' operator for a specific five digit zip code selects zip and zip+4.

Labels can be removed on the data display forms only. Labels must remain on the data maintenance forms so that the user will be able to determine what field he or she is entering data for.

It is by design that after adding custom lookup fields to the relation screen in the Customizer, the relationship row belonging to the second party is not being created as a 'mirror' image.

Documentation has been clarified to remove the word 'mirror' in the topics in which it occurred. In addition, the Custom Lookup Tables and Fields topic now states the following:

There are areas in the software where, if a data row is created for a constituent, an almost identical, reverse data row is automatically created for a second constituent. Creating Screener and Relation rows are two examples of this. Most of the information in the Standard fields in the first constituent's data row is copied to the second constituent's data row. However, the information in the custom fields will not be copied to the second constituent's data row.