Millennium Release 7.2.1 |
|||
|
|
> |
The following items are included in Release 7.2.1. Note that some items are enhancements to the software and some are corrections. The correction items describe the symptoms that you might have encountered, PRIOR to the installation of this release.
System-wide Changes
Interface - Database |
Function |
Description |
Both/Both |
Lookup Table Caching |
The caching of the lookup tables has been changed from the standard ANSI character set order to a sort that is not case-sensitive. This may affect the order in which lookup table entries appear in pull-down list boxes as compared to previous releases. |
Both/Oracle |
User Accounts |
The default Temporary Tablespace for user database accounts has been switched from MILLREPORTS to TEMP. |
Installation Corrections
Remember that the descriptions for the following items describes the problem PRIOR to the installation of the corrections as part of the current service pack.
Posted Date Reported Problem # |
Function |
Database |
Interface |
Description |
|
Membership Dates |
All |
Both |
To bring certain Membership date fields into conformity with their current definitions, scripts are available as part of 7.2.1 to re-calculate the membtypddt and membinitdt columns, for any Membership rows which contain data in those columns. Membtypddt is the earliest date that the constituent joined a Membership of the same type, and membinitdt is the earliest date that the constituent joined a Membership of any type. Institutions may choose at their option to run either or both scripts, first to print for verification a list of data rows which would change, then (with a minor edit to the script) to re-run them to actually edit the data in the field. |
6/13/2002 9. |
Update primary Key on report_descripts |
All |
Both |
If you have multiple reports with the same name in the same report group, you will get an error message which states: subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <=, >, >= or when the subquery is used as an expresson. |
05/22/2002 8. |
Millennium 7.2 System Configuration.doc |
All |
Both |
On page 6 in the URLScan.ini Settings paragraph it currently reads: Comment exe out of Deny Access paragraph of URLScan.ini.. It should read: Comment exe out of DenyExtensions paragraph of URLScan.ini.. |
05/01/2002 7. |
Importing sample database |
Oracle 8i only |
Both |
Importing the orasample 72.dmp results in an error that the user must be a DBA to import the database. The import file was created from a database where the user MILLORA has the DBA role. This in not required for Millennium to function correctly. |
5/01/2002 6. |
Sample database |
SQL Server |
Both |
The GENERIC and GENERIC_EVENT tables are in lowercase in the millsample database. When adding a new group in group security this will result in an error. |
04/26/2002 5. TS #: 1878 |
Queue as a Service |
All |
Both |
When setting up a Queue as a service, and checking the Domain Name radio button at the top, it still allows you to check the "Create User on Additional Computer" box below even though the "Additional Computer" box is grayed out. |
04/26/2002 4. |
Queue and Millennium IIS |
All |
Both |
When installing the Queue on a machine that currently has the Millennium IIS software installed, the Queue installation overwrites the current Millennium IIS installation with the Millennium IIS files from the install CD. When installing the Millennium IIS on a machine that currently has the Queue software installed, the Millennium IIS installation overwrites the current Queue installation with the Queue files from the install CD. |
04/23/2002 3. |
Easy Ask |
All |
Both |
For EasyAsk to install correctly the Windows Scripting Host (WSH) must be installed and functional on the IIS. |
04/18/2002 2. |
Millennium 7.2 System Configuration.doc |
All |
Both |
On page 2 of the Millennium 7.2 System Configuration.doc the information for the Netscape Communicator (Macintosh) is incorrect. The correct information is in the Millennium 72 Software Environment.doc on the installation CD. |
04/15/2002 1. |
Sample Database SQL Server 2000 Named Instance |
SQL Server 2000 |
Both |
The automated install of the sample database will not work if SQL Server 2000 is installed with a named instance. The automated install will report that SQL Server is not installed. |
Profiles Enhancements
Interface |
Function |
Description |
Both |
Added Credit |
If a 'Credit for Other' transaction is added to an existing one that was Tendered as Credit Card, Gift in Kind, or Securities, the insert form for the Credit transaction will default to the same Tender Type, but the system will not prompt for the creation of an additional secondary row for Credit Card, Gift in Kind, or Securities linked to the Credit row. |
Both |
Attachments |
In order to enforce the system's security settings for Attachments, the option, Unlink Attachments has been removed from the Special menu (Browser) and the context menu (Windows). You may still perform the functional equivalent by simply deleting individual Attachment rows. Note that the Attachment row only serves as the means of tracking the link from the primary data row to the source file. Deleting the Attachment does not delete the source file. |
Both |
Basic Data |
The system will now interpret any Group other than C/Corporation or F/Foundation that is associated with the Constituent Type as a 'person', for the purpose of choosing the kind of Basic Data display and maintenance forms to be used. (Previously, the group had to be blank.) This allows you to categorize the Constituent Types for people, for your own purposes. Corporations and Foundations must still be C or F to trigger the use of the appropriate forms for Basic Data. |
Both |
Basic Data Constituency Type |
If the Constituency Type is edited in a way that changes the constituent from a person to a corporation or other (based on the information in the Group field of the entries in the Constituent Type lookup table), or vice versa, the system will automatically edit the Basic Data row and remove the data from fields that do not apply to the new Constituent Type. If the type is changed from Person to Corporation or Other, those fields are: coresex, coremaritl, corechflag, corechnum, corebirthd, coressnum, coreparpyr, coreparsch, coreprefyr, coreprfsch, coreethnic, corebcntry, coregrnpyr. If the type is changed from Corporation or Other to Person, those fields are: coreindust (Corporation only), corefntype (Foundation/Organization Only), coretotemp, corekwnemp, corealmemp, corerlkey1, corerlkey2, corecorpid, coreallsub, corekwnsub, corepropm1, corepropd1, corepropm2, corepropd2, corepropm3, corepropd3, coremduem1, coremdued1, coremduem2, coremdued2, coremduem3, coremdued3, coremduem4, coremdued4, coremnamt1, coremxamt1, coremrat1, coremnamt2, coremrat2, coremnamt3, coremxamt3, coremrat3, matchcomm, coremtchid. |
Windows |
Comments |
When data is displayed in either the Profiles or Events World, Comments that are part of another data row, or independent Comments display in green. |
Both |
Adjustments have been made to the behavior of the Default Batch # to ensure consistency between the Browser and Windows interfaces. Both now behave as follows: If you have identified a Default Gift or Dues Batch #, that number is automatically used in the Insert form for Gifts or Dues. If you also want to use the Default Batch # when Inserting Via Default, you should enter the word, 'DEFAULT' (minus quotes) in the Batch # text box in the form used to create the Gift or Dues default. When you access the default form to create the Gift or Dues row, the default Batch # will automatically have been substituted in the form. |
|
Windows |
Gift and Dues Data Entry Default Account |
The Default Account functionality has been activated in the Windows interface. When defining a Gift or Dues default, you may now enter 'DEFAULT' (minus quotes) in the Purpose text box in the form. The system will accept that text, even though it does not match any entry in the Chart of Accounts. When you access the Gift or Dues Default to create a data row, DEFAULT will appear in the Purpose text box. You should not edit that box (or the Acct # text box in the Windows form) unless you want to choose another account other than that constituent's Default Account, as found in the Basic Data row. When you insert the data row, the system will substitute the constituent's Default Account for the Purpose. (This functionality was already available via Browser.) |
Both |
Linked Addresses |
If the non-displaying fields, addrlat, addrlong, addrlot, and addrbarcde are edited, the corresponding fields in any linked Addresses will also be edited. (This functionality is applicable to the use of CorrectAddress.)© |
Both |
Match Pledge and Match Potential |
When creating a Match Pledge or Match Potential, the insert form will no longer use the Check # data from the original as default info for the matching transaction. |
Both |
Membership Dates |
The dates in the Automated Membership Process that are used by default or are calculated based on existing Membership data have had further refinements to ensure consistency. |
Browser |
Profile Reports |
A set of standard, on-demand reports are available from within the Profiles World. From a new 'Reports' button shown in the constituent display header, you are shown a pop-up menu of the names of these reports. When you select one and click OK, the report is immediately executed for the current constituent. The results are displayed in a new instance of the browser, in pdf format, using an Adobe Acrobat viewer. You may use the viewer tools to search the report, print, navigate from page to page, zoom, and otherwise alter your view of the information. To make use of these reports, the client machine must have Adobe Reader installed. This is a free download, available at http://www.adobe.com/products/acrobat/readstep2.html. (This compares to the functionality available via the Windows interface's File, Run menu.) |
Both |
Relation Create Date |
To satisfy a conversion need, a change has been made to the internal system trigger which populates the relcrdate field on a linked Relationship. Previously, this was always set to the current date. It is now set to populate that field with the same relcrdate from the primary Relationship row. (Used in the conversion process of historical data.) |
Browser |
Search Results |
It is now possible to save the results of either a standard or an advanced search in the Profiles World. When results are displayed, two buttons are shown below the data, labeled Save Results and Load Results. If you click Save Results, a pop-up window will prompt you to enter a filename for the worktable that will be created, using the generic worktable layout. Saved search results may be retrieved for display as a Profiles Search results by clicking the Load Results button on the initial search form or on the search results display page. In either case, a pop-up window will display the names of all of the saved search results as well as all saved worktables that were created via the run of a set of criteria in the Reporting World that are 'owned' by your User Id. Saved search results from the Profiles World may be used in the reporting feature, Use Existing Worktable. Note that the saved search results worktables are subject to the same 500 row limit that is enforced as a maximum for the search results display. |
Both |
Spouse Relationship |
The system will check and prevent the creation of multiple spousal Relationships. This includes: Spouse; Spouse, Separate Mailing Address; Life Partner; and Life Partner, Separate Mailing Address. |
Both |
Unspecified Pledge and Pledge Potentials |
When 'unspecified' Pledges (those having an amount of $0) or Pledge Potentials are entered, the system will no longer prompt for the input of additional Pledge info, usually used in the creation of entries in the Payment Schedule. |
Both |
Update/Archive Addresses, Ratings, PG Ratings |
The behavior of the Update/Archive function for Addresses, Ratings, or PG Ratings has been enhanced to do the following: 1. If the original data row that is being updated does NOT have a Stop Date filled in when you begin the Update/Archive process, the Start Date that is specified in the insert form for the new data row will be used as the Stop Date of the old row. This will either be the current day's date that the system uses by default, or another date that you entered manually for the Start Date. 2. If the original data row that is being updated already has a Stop Date filled in when you begin the Update/Archive process, that date will not be changed in the original row. It will also be used as a default for the Start Date in the form for the new data row that is being created, though you may edit that date prior to inserting the new data row, if desired. |
Both |
User Match Options |
The system will now only invoke the User Match Option for the treatment of Match Potentials when the original transaction is a Gift/Dues (g) or Pledge Payment (y), (and when the Post Match checkbox is not checked on the original transaction's insert form.) You may still create Match Potential or Match Pledge transactions for other Transaction Types but the system will not automatically search and prompt for them during insert |
Both |
Volunteer |
To avoid confusion, the Volunteer item has been removed from the Millennium Explorer until such time as that data table is activated in Millennium. |
Profiles Corrections
Remember that the descriptions for the following items describes the problem PRIOR to the installation of the corrections as part of the current service pack.
Posted Date Reported Problem # |
Function |
Database |
Interface |
Description |
06/26/2002 46. TS#: 1361 |
Gift display |
All |
Windows |
If a constituent has an exceptionally large number of gifts, accessing the display may result in an overflow error. |
06/26/2002 45. TS#: 2340 |
Inserting Screeners |
All |
Windows |
When inserting a screener (via default or normal insert), if the name field is left blank, you will get an "SQLExecDirect Error" in the Windows client instead of being prompted to select a Name/ID. |
06/26/2002 44. TS#: 2409 |
Gift default batch number |
All |
Windows |
If the batch # in the gift default is blank and the batch number default is defined, when you insert a gift using the default, the batch number text box uses the default batch number. For the new behavior, see Profiles Enhancements, Default Batch Number. |
06/21/2002 43. TS#: 2548 |
Address types for email and Web sites |
All |
Windows |
In browser, Millennium recognizes any address_type that starts with "email" as an email address and any address_type that starts with "www" as a web address. Windows only recognizes the address_type "email" as an email address and the address_type "www" as a website address. |
06/21/2002 42. |
Inserting linked addresses |
All |
Both |
When inserting linked addresses the fields addrlat, addrlong, addrlot, and addrbarcde were not being copied from the primary address row to the linked address row. If the non-displaying fields, addrlat, addrlong, addrlot, and addrbarcde are edited, the corresponding fields in any linked addresses will be updated accordingly. (These fields are not part of the standard display or maintenance forms, but are used by CorrectAddress.) |
06/19/2002 42. |
Inserting Non-constituent Relationships |
All |
Both |
Inserting a non-constituent relation results in the following message: Server: Msg 30002, Level 16, State , Procedure ti_relation, Line 312 Xñ-. |
6/13/2002 41. TS#:2377 |
Post Payment Form |
All |
Windows |
The post payment form does not have a text box for the deductible amount. |
6/10/2002 40. TS#: 2292 |
Address Single Line Display |
All |
Windows |
When you have Addresses in single line display, you cannot access the Phone display. |
6/10/2002 39. TS#:2342 |
Update Outlook |
All |
Windows |
When you set the update Outlook option to be checked, if you exit Millennium and log into Millennium as the same user, the update Outlook check box is unchecked. |
6/10/2002 38. TS#: 2355 |
Journal and Correct |
All |
Both |
When you journal and correct, you are not allowed to change the batch number of the journaled transaction. |
6/03/2002 37. TS#: 2270 |
Single Line Display |
All |
Windows |
When you go to a defined single line display and clear all from the display and click Ok, Millennium will go to the last defined single line display. If you go back to define a single line display, there are no fields in the display. |
6/03/2002 36. TS#: 2271 |
Inserting Journals |
SQL Server |
Both |
When you click insert several times on the journal screen, Millennium will create a row for each time you click insert. If you delete one of the journals, it will delete that journal and the void. All of the extra journal records remain in the database. |
05/31/2002 35. TS#:2264 |
Displaying journals and voids |
All |
Windows |
In the Windows client, the display of journals and voids is not responding to the setting for the user option to display or not display journals and voids. |
05/31/2002 34. |
Advanced Search |
All |
Browser |
When performing an Advanced Search using the Employer Name field (jobsconame), the system does not offer the comparisons, 'contains', 'does not contain', or 'never contains'. |
05/31/2002 33. TS#:2182 |
Letters |
All |
Windows |
When using the Letters function in the Windows interface on a client machine with Word 97, you get a message stating that you must be using Word 2000. |
05/21/2002 32. TS#: 2146 |
Match Potential Write-off |
All |
Both |
When a Match Potential is written off, the write-off is not correctly reflected on the original donor's transaction. |
05/15/2002 31. TS#: 2105 |
Non-constituent Honoree |
SQL Server |
Windows |
When inserting a non-constituent Honoree, the Comment text box only allows you to enter 10 characters. |
05/15/2002 28. TS#: 2104 |
Posting Pledges |
All |
Windows |
When posting a pledge payment, the correspondence pull-down text box displays the Correspondence Type lookup table rather than the Correspondence Name lookup table. |
05/10/2002 27. TS#: 1989 |
Membership |
SQL Server |
Windows |
When you enter a membership and you are processing by membership, you will get a type mismatch error. When you enter a membership and you are processing by dues and field(s) on the dues insert screen are left blank, you will get type mismatch error. |
05/10/2002 26. TS#: 2043 |
Gifts insert |
SQL Server |
Windows |
When inserting a gift and receiving an exact hit on the account number to find the purpose, the purpose box is populated with the correct account, but the account number box becomes blank. |
05/10/2002 25. TS#: 2042 |
Gifts insert |
SQL Server |
Windows |
When inserting a gift and receiving a partial hit on the account number, there is a list of account numbers returned, and you then you press the down arrow, focus is moved to the next box in the tab order. |
05/08/2002 24. TS#: 2035 |
Journal and correct |
SQL Server |
Windows |
When using journal and correction in windows, the payment is journaled correctly, however the correction that is created is a bequest and there is a void transaction attached to it. |
05/08/2002 23. TS#: 2013 |
Event tasks and Outlook |
SQL Server |
Both |
When you have the option to update tasks in Outlook selected and you insert an event task, the task is not added to the task list in Outlook. |
05/07/2002 22. TS#: 1958 |
Single Line Display |
SQL Server |
Both |
In single line display when you right click and select edit from the menu, nothing happens. |
05/07/2002 21. TS#: 2002 |
Pledge Payment Schedule |
All |
Both |
When you enter an invalid date in the start date when creating a pledge, no error message results. The pledge schedule is created without due dates on the payment rows. Note: With 7.2.1, error checking has been added to the giftstrty and duesstrty (Start Year), and giftstrtm and duesstrtm (Start Month). Note that if invalid data is already present in existing pledge rows, any edits to that row (including posting a pledge payment against it) will trigger that error message. |
05/07/2002 20. TS#: 1977 |
Relation Defaults |
SQL Server |
Both |
When you set defaults for relations to be a non-constituent relation row, inserting using the default returns a SQL 'insert into' error. |
05/02/2002 19. TS#: 1978 |
Address Defaults |
All |
Both |
Millennium was updating an address whenever any address was inserted using the default because of bad data in the address default. |
05/02/2002 18. TS#: 1978 |
Update/archive Addresses |
SQL Server |
Both |
If you have linked spouse addresses with one as the preferred address and one not preferred, when you update/archive one, the link disappears and the other spouse address does not update. Could not duplicate the reported error. |
05/02/2002 17. TS#: 1564 |
Lookup Tables |
All |
Windows |
When selecting data from lookup tables using values rather than codes and the values are very similar, but using different cases, the code inserted in the data may not be the code for the value selected. |
05/02/2002 16. TS#: 1954 |
Journaling Gifts and Dues |
All |
Windows |
When journaling a record, you get an Millennium Gift Control dialog that states: *SQL ProessStatment General Error: Login failed for user 'ml'. Login failed for user 'ml'. Statement: DSN=Web SQL;UID=ml;==Select * from name_full WHERE nameid = '0000000262' ORDER BY nametype. This problem is only on clean installs of Millennium 7.2 (not upgrades). |
04/25/2002 15. |
Linked Addresses |
SQL Server |
Both |
Updating/archiving a linked address that is linked to only one other address would cause one side of the linked address to be unlinked. |
04/24/2002 14. TS#: 1768 |
Names |
All |
Browser |
Once a Name row is created with one of the long override Names, if you access an edit form and make other edits, the data in the override text box (past 72 characters) is truncated. |
04/24/2002 13. TS#: 1768 |
Names |
All |
Browser |
When you get an edit form for a Name row that has a very long name in one of the override text boxes (over 72 characters), the form doesn't include all of the data for that field in that text box - only the portion that can be displayed. |
04/24/2002 12. TS#: 1768 |
Names |
All |
Both |
You can enter valid data (110 characters) in the salutation, combined salutation, or combined formatted name text box that exceeds the display limit (72 characters). The display should display all 110. |
04/23/2002 11. TS#: 1836 |
Bequest Transactions |
SQL Server |
Windows |
When entering a bequest transaction, the display shows the word, 'Balance' rather than the word, 'Amount' and the giftamount displays in red, rather than green. |
04/22/2002 10. TS #: 1844 |
Addresses |
All |
Windows |
When entering an Address with no Utilizations checked, the Address display is blank for Address Utilizations. Should display the word 'None'. |
04/22/2002 9. TS #: 1200 |
Gifts |
SQL Server |
Windows |
When you add a match pledge/potential or add a credit and you are using the custom date field, the default date in the insert screen is Jan 1, 1900. |
04/22/2002 8. TS #: 1798 |
Jobs |
Oracle |
Both |
When updating the job status, the industry will be set to blank. |
04/16/2002 7. TS #:1691 |
Gifts |
All |
Both |
When adding an in-honor transaction to a transaction that has the same 'trnum' but different 'cruser' as another transaction, the honor transaction will be linked to the first found transaction with the matching 'trnum'. |
04/15/2002 6. TS #: 1517 |
Journaling |
All |
Both |
When journaling a pledge payment transaction on the second allocation, the paid amount on the payment schedule is not updating. |
04/15/2002 5. |
Membership |
All |
Browser |
Renewal of an active Membership to the same Type is calculating the default Expiration Date as the date of the previous active Membership plus twice the duration of the new. |
04/15/2002 4. |
Membership |
All |
Both |
Re-joins that change Membership Types are defaulting to simply 'Re-join', not 'Rejoin Upgrade' or 'Rejoin Downgrade'. |
04/15/2002 3. |
Membership |
All |
Both |
If there is no Renewal Setup Day in the Membership Type lookup table and the Renewal Setup is RF, the default Expiration Date is not correct. It calculates as the Dues Day plus duration, rather than rolling to the first of the month. (Calculates ok if there is a Renewal Day filled in.) |
04/15/2002 2. |
Correspondence |
All |
Windows |
If a Correspondence data row is inserted without identifying a 'Sent By' constituent, the subsequent Edit maintenance form will be the Non-constituent version. |
04/15/2002 1. |
Membership |
All |
Both |
If you change the status on a Membership Type to N in the membership_type lookup table, the system still allows you to insert that type if the constituent has that membership type and the system picks it as the "best-fit" membership. |
Events Enhancements
Interface |
Function |
Description |
Both |
Guest Name |
A new, standard Name Type has been added to the Profiles World called Event Name (code: 'event'). When a constituent has a Name row of that type and an Event Guest row is being created, the Event Name, rather than the Preferred Name, will be defaulted into Name Tag Line 1 in the form for the Event Guest. The preferred name will still be used for the name text boxes at the top of the form. If no Name row of that type is found, the Preferred Name will be used for both the text boxes at the top of the form and the Name Tag Line 1 text box, as previously. |
|
|
|
Browser |
Event Guest Display |
Activity Items are now being shown with the Event Guest information in the Registration Detail display. |
Both |
Other Info Display |
The Single Line display option has been disabled for the various forms of the Other Info data table (Audio Visual Needs, Lodging, Tourney, etc.) |
Events Corrections
Remember that the descriptions for the following items describes the problem PRIOR to the installation of the corrections as part of the current service pack.
Posted Date Reported Problem # |
Function |
Database |
Interface |
Description |
06/26/2002 11. TS#: 2111 |
Registrants with Guests Report |
All |
Browser |
The Events Registrants with Guests report displays a "Page Cannot Be Displayed" message after clicking the hyperlink. |
06/26/2002 10. TS#: 2568 |
Seating Layout |
All |
Windows |
When using assign all in Seating Assignment to assign Seats to individuals and then using the drag feature to move individuals from one seat to another, individuals who have not been touched will return to the unassigned list (they disappear from their seat!). The drag feature is particular about the placement of the individual over the seat and it appears that after many attempts to place an individual in a seat is when others will return to unassigned and disappear from their seat. |
06/26/2002 9. TS#: 2572 |
Data Indicators |
All |
Windows |
When inserting rows in the data tables in Events and Activities, the indicator lights will not light until you exit and return to Millennium. |
06/26/2002 8. TS#: 2570 |
Viewing Activities |
All |
Windows |
If the number of activities to display exceeds the available window in the applet, no scroll bar is available to see the remaining list. |
06/26/2002 7. TS#: 2554 |
Linked Task |
All |
Windows |
In the event/activity action screens when a linked task is created, a hyperlink is also created to the person's assigned task. If you click on the hyperlink, it takes you to the last profile screen viewed for that person rather than to that person's task screenas expected. |
6/13/2002 6. TS#: 2253 |
Deleting Events |
Oracle |
Both |
Deleting an Event in Oracle may generate a 'Table is mutating' error message. |
6/10/2002 5. TS#: 2364 |
Inserting Registration |
All |
Windows |
In the registration process, the 'Attended' checkbox is missing from the Attendance insert form. |
5/31/2002 4. TS#: 2263 |
Seating Layout |
All |
Windows |
When you have an Attendee for an Activity with stadium seating in the Windows interface and try to assign the Attendee to a seat, you get an automation error. |
05/08/2002 3. TS#: 2027 |
Registration Custom Templates |
All |
Browser |
When using a custom template that has regyesno field on it and you edit a registration, any changes made to regyesno are not updated. |
04/15/2002 2. |
Seating Layout |
All |
Windows |
The list of Attendees displayed in Seating Layout maintenance may become out of sync with the name of the Activity shown in the header for the Seating Assignment function. This problem is avoided by choosing an Activity in the Millennium Explorer, and then going directly to the Seating assignments function. |
04/15/2002 1. |
Registration Fees |
All |
Windows |
The system does not permit the creation of a Registration Fee data row until or unless there are Guests attending Activities (and therefore a default Registration fee can be calculated.) |
Reporting Enhancements
Interface |
Function |
Description |
Both |
Event Reports |
To avoid an issue with the length of the Event Code (10 characters), the Reporter automatically displays the Event Name rather than the Event Code when constructing report criteria. |
Both |
Export |
The layout of the export file that is generated using the 'Export option when no Crystal format is specified' feature (introduced in Release 7.2) has been adjusted to have the field names listed as the first row of data. This is the case for both CSV and Tab Delimited files. |
Both |
Print Criteria |
Two changes have been made to the Print Criteria function of the Millennium Reporter's Run Options. The information that is printed via the Print Criteria function now includes both the selected values for any report parameters and any prompted replies that are part of the set of criteria. When the Print Criteria is activated, if the report destination is a specific printer, the criteria information will also be printed at that printer (rather than at the default printer, as was previously the case.) If the report destination is not a printer, but the criteria are to be printed, the default printer will used. |
Both |
Saving Worktables |
When running a report and you choose to save the worktable, the system prompts you to name the saved worktable by presenting a list of existing table names and a text box for the name you want to re-use or create. With this Service Pack, the list will include the existing worktable names, only. Previously, this list included the names of saved criteria tables. |
Reporting Corrections
Remember that the descriptions for the following items describes the problem PRIOR to the installation of the corrections as part of the current service pack.
Posted Date Reported Problem # |
Function |
Database |
Interface |
Description |
06/26/2002 7. TS#: 2187 |
Displaying reports |
All |
Windows |
At some sites the reports don't appear when you first click on them. |
06/21/2002 6. |
Export to pdf |
All |
Both |
If you are exporting to pdf on a reporting server without a full install of Crystal, PDF fails to export. |
6/13/2002 5. TS#: 2124 |
Report Groups |
All |
Both |
If you have multiple reports with the same name in the same report group, you will get an error message stating that the subquery returned more than 1 value. |
5/31/2002 4. TS#: 2172 |
Creating Criteria |
Oracle |
Both |
When creating new criteria in Oracle, you may receive an error message stating that the data source could not be opened, and that the table or view does not exist. (The report_options table is missing the public synonym.) |
5/31/2002 3. TS#: 1854 |
Queue as a Service |
All |
Both |
The queue as a service will not add the queue user as a domain user. When you submit a report to the queue running as a service, the report remains idle. |
05/14/2002 2. TS #: 2076 |
Deleting Reports |
SQL Server |
Windows |
When you delete a report in the windows client, the report is deleted, but the record in report_descripts is not. |
04/15/2002 1. TS #: 1640 |
Printers |
All |
Both |
When you edit a printer on the sysinfo page with an '&' in the printer_name, a page not found error results. |
Tools Enhancements
Interface |
Function |
Description |
Both |
Constituent Type Lookup Table |
The Basic Data display and maintenance forms vary in accordance with the Group associated with the Constituent Type. Previously, the system looked for a blank Group for persons, a Group code of C (Corporation), or F (Foundation). With Release 7.2.1, the Group may be filled in for persons, to allow you to categorize your Constituent Types for your own purposes. Any Group code OTHER THAN C or F will be interpreted to be a person. This includes a blank Group. Those with a Group code of C or F will continue to be interpreted as Corporations or Foundations. |
Windows |
Lookup Maintenance |
The Comments on the display of lookup table entries now display in green, as in the Comments in data. |
Both |
Membership Type Lookup Table |
The Maintenance form for the Membership Type lookup table has some changes. The names for the Renewal Setup options have been changed to use the word 'Year' rather than 'Month', for Calendar and Fiscal Year Memberships. Those three options are now labeled: Calendar Year Membership, End of Year The Deductible Amount text box has been removed from the standard Windows maintenance form for this lookup table, as that field is not currently in use in the software. |
Both |
System Info |
The Millennium Reporting Information on the System Information display now includes 'Default Export Path'. This allows the institution to create a default UNC path location for the export of data via Crystal (not the location of published reports). |
Tools Corrections
Remember that the descriptions for the following items describes the problem PRIOR to the installation of the corrections as part of the current service pack.
Posted Date Reported Problem # |
Function |
Database |
Interface |
Description |
06/26/2002 8. TS#: 2537 |
Table Maintenance |
All |
Windows |
When inserting a Territory in the Table Maintenance for Profile Lookups and then going over to the Zipcode Table and edit a zipcode, the Territory drop down list is blank. |
6/13/2002 7. TS#: 2382 |
Changing MILLORA Password |
Oracle |
Browser |
When trying to change the password for the MILLORA User Id only, you get the following message: Display Failed: Couldn't open data source ORA-01017: invalid username/password; logon denied Driver's SQL SetConnectAttr failed. |
5/31/2002 6. TS#: 2278 |
Generic Import Utility |
All |
Both |
The sample dbf that is provided for use with the Generic Import utility is not updated to include the additional data fields that were added to the utility in 7.2. |
5/31/2002 5. |
Public synonyms.exe |
Oracle |
Both |
Public synonyms.exe does not create the synonyms for the tables: REPORT_AGENT |
05/13/2002 4. TS#: 2050 |
Lookup Table Maintenance |
All |
Windows |
In lookup table maintenance, if you do a search with the sort on code and search by a value, the search will not work. |
05/01/2002 3. TS #: 1914 |
AssignSummary |
All |
Both |
The utility does not close when using the X in the upper right-hand corner of the dialog box. |
04/30/2002 2. TS#: 1924 |
User Security |
SQL Server |
Browser |
When you change a user's password using the Browser interface, the password does not change. Password can be changed in the Windows interface. |
04/22/2002 1. TS#: 1821 |
Group Security |
SQL Server |
Windows |
In group maintenance, the custom tables for FFB are showing up in the group security component of the windows client. This will cause errors if someone updates group security information. |
Reference Corrections/Enhancements
Remember that the descriptions for the following items describes the problem PRIOR to the installation of the corrections as part of the current service pack.
Posted Date Reported Problem # |
File Name |
Description |
Correction |
Dues_Detail.html |
Sustainer Pledge transaction types are available for Gift transactions, and do not apply to Dues. The documentation has been updated to remove references to Sustainer Pledges from the Dues data table and Dues Transaction Type lookup table descriptions. |
Correction |
Gift_Detail.html Dues_Detail.html |
The description of the Honor transaction type is incomplete. It should read as follows: 'Indicates that a transaction has been made in honor or memory of this constituent. When linked to another transaction, this type is generated by the system and should not be entered manually. Independent Honor transactions may be entered manually.' |
Correction |
Import_Utility.html |
In the file layout for Import.dbf, the names of the business mailcodes did not include the numbers. All were shown as BMAIL rather than BMAIL1, BMAIL2, etc. |
Correction |
Lookup_Layouts.html |
The description of the layout for the Chart of Accounts omitted the custom data fields and the chart_dprt field. |
Correction |
Mergeid.html |
The description of the Merge Id utility now includes information and instruction about the utility's behavior regarding Summary rows. (Summary rows are not moved by the action of Merge Id.) |
Correction |
Membership_Card.html |
The field description section for the Membership Card table incorrectly included a field named 'cardnumber'. This field is not currently part of the Membership Card data table and that reference has been removed. |
Correction |
Pledge_Reports.html |
The description of the criteria for the six Cash Forecast reports incorrectly indicated that only pledges with a balance remaining to be paid would be selected. The criteria selects all transactions with a type of pledge. |
|
|
|
Correction |
System_Tables.html |
The documentation for the system tables now includes the information on the indices for each table. |
Correction |
User_Defined_Scripts.html |
The description of User Defined Scripts now includes information regarding the use of Parameters and the specification of the Custom Workfile Name used. |
04/15/2002 1. |
Basic_Data.html |
The description of the COREREST field in the Basic Data table is incorrect. It states that there should not be a blank in the Chart of Accounts lookup table, when in fact there should be one, though it does not have to be active. |
Enhancement |
Table of Contents |
Report Templates, a new entry in the table of contents for the online Help files makes it easier to access the documentation for the standard Millennium reporting templates. |
Database and System Changes
Interface |
Table |
Description |
All |
sysinfo report_options |
A field has been added to the sysinfo and report_options tables, each named default_UNC. These are 128 character columns, used to track the location of the reports that will be used as the default in the Run Options form. |
All |
report_descripts |
The primary index now includes report_group at the end. |
All |
systemtemplate |
The sysstring field increased to 4000 characters. |