Bug/Problem
Report Format
Description of severity codes
| Program | Member View |
| Version | Version 0.18 Release Date 07/24/98 |
| Applies to | V0.18 and earlier. Search combo boxes. |
| Description | Small memory leak. |
| Found date | 07/25/98 |
| Found by | D.Wachtel |
| Status | Fixed in V0.19 |
| Problem | The leak was small enough that no problems occurred under normal
circumstances. When search lists were pruned, storage for an object instance was not being freed by the list element delete method. Explicit destruction of the object instance in each list element has been added to free the storage allocated for each object instance. |
| Severity | Minor |
| Fix/Workaround | Fixed V0.19. Storage is freed properly. |
| Fixed By | D. Wachtel |
| Fixed Date | 07/25/98 |
| Program | Member View |
| Version | Version 0.18 Release Date 07/24/98 |
| Applies to | National file browser Version 0.18 and earlier versions containing the browser. |
| Description | File in use error |
| Found date | 07/26/98 |
| Found by | D.Wachtel |
| Status | Fixed in V0.19 |
| Problem | Opening the same file twice when the second opening used the browse for files command rather than picking the file from the database table caused a file sharing error. |
| Severity | Minor |
| Fix/Workaround | Fixed V0.19. Open table was not closed in browse for file command when a new file was selected. It now is closed properly. |
| Fixed By | D. Wachtel |
| Fixed Date | 07/26/98 |
| Program | Member View |
| Version | Version 0.18 Release Date 07/24/98 |
| Applies to | V0.18 and earlier. People View Address Tab |
| Description | Key Violation sometimes reported when adding a new address. |
| Found date | 07/24/98 |
| Found by | D.Wachtel |
| Status | Fixed in V0.19 |
| Problem | When this problem occurs, the value held in the nextaddr table is one less than the highest allocated address key. When the next address is created and a post is done, a key violation results. This may be related to a similar problems that occurred recently at the Atlanta beta test site. |
| Severity | Moderate to severe |
| Fix/Workaround | Fixed V0.19. The key number is now verified before creating a record. |
| Fixed By | D. Wachtel |
| Fixed Date | 07/25/98 |
| Program | Member View |
| Version | Version 0.18 Release Date 07/24/98 |
| Applies to | V0.18 and earlier. Reading National files, Merging and importing from external records |
| Description | Occasionally a person is linked to another address in error. |
| Found date | 07/24/98 |
| Found by | D.Wachtel |
| Status | Fixed in V0.19 |
| Problem | Sometimes a member will be linked to the wrong address when there are
similarities between the name and address. This happens because the matching algorithm is
finding a match in error. Bad linkages will occur about once for every 100 members read. Checking addresses "by hand" in the Places view shows the addresses that are linked in error. These have multiple occupants of the same address that are obviously incorrect. |
| Severity | Severe |
| Fix/Workaround | Fixed V0.19. Instance variables needed to be fully qualified. A boolean result was not being assigned to a method. |
| Fixed By | D. Wachtel |
| Fixed Date | 07/26/98 |
| Program | Member View |
| Version | Version 0.17 release Date 07/10/98 |
| Applies to | V0.17 only. Reading National files, Merging and importing from external records |
| Description | Invalid e-mail addresses and interests reported. |
| Found date | 07/24/98 |
| Found by | D.Wachtel |
| Status | Fixed in V0.18 |
| Problem | When this problem occurs, the e-mail and interests reported to be invalid are correct. They do not get put into the database. Each error puts up an error dialog that must be dismissed with OK. Apparently the check for non-ASCII characters in fields, put in as an additional protection against corrupting the target database, reports an error by mistake. |
| Severity | Moderate |
| Fix/Workaround | Fixed V0.18. The checks for valid characters was done using an incomplete collating sequence. The has been replaced with the proper sequence. |
| Fixed By | D. Wachtel |
| Fixed Date | 07/24/98 |
| Program | Member View |
| Version | 0.16 |
| Applies to | Reading data files and inserting records |
| Description | Post errors, key violations |
| Found date | 06/15/98 |
| Found by | G.J. Atlanta Region, SCCA |
| Status | Partial fix in 0.17, complete fix in V0.19 |
| Problem | Under some conditions a duplicate key error will be reported when trying to insert a record. |
| Severity | Severe |
| Fix/Workaround | Member view is still mostly usable, but new records of the type that
crashed cannot be entered. Running TUtil32.exe on the DB tables and restarting MV or
starting up a read of a national data file (you can abort the read after the first record
is read) may fix the problem. Hand editing the offending tables after verifying the
integrity of the tables will also fix the problem, but should only be done by CSI
personnel. Fixed in version 0.19 |
| Fixed By | D. Wachtel |
| Fixed Date | 07/24/98 and 07/26/98 |
| Program | Member View |
| Version | 0.16 |
| Applies to | Any operation that opens tables |
| Description | EDBEngineError Too many open cursors |
| Found date | 05/98 |
| Found by | D.Wachtel |
| Status | This is a configuration problem that is fixed by changing settings. |
| Problem | Too many open cursors means that there are too many file handles being requested. The number of available file handles is set in the BDE configuration dialog. |
| Severity | Severe |
| Fix/Workaround | Exit Member View and start up the Database Engine Configuration tool. Change to the System tab. Find the entry for MAXFILEHANDLES. The value will probably be something like 16. Change it to a number greater than 48. On the main menu, select File->Save to save the BDE configuration. Then select File->Exit to dismiss the tool. If the problem still occurs, you need to edit the config.sys file line FILES=xx where xx is some integer. If the line is missing, then type in FILES=60 without the quotes of course. If the line is present and the number is less than sixty then change the number to sixty. |
| Fixed By | NA |
| Fixed Date | NA |
| Program | Member View |
| Version | 0.16 |
| Applies to | People Window |
| Description | When tabs are selected sometimes the contents does not update. |
| Found date | 05/98 |
| Found by | Dave Wachtel |
| Status | Open |
| Problem | There is a sporadic problem with updating tab contents under some combination of conditions that are still to be determined. The fields remain blank even though there is data that should be displayed. This is particularly common in the personal data tab. |
| Severity | Moderate |
| Fix/Workaround | The workaround is to select another person, then select the desired person again. The blank fields should update. |
| Fixed By | |
| Fixed Date |
Blank Bug/Problem report table
| Program | Member View |
| Version | |
| Applies to | |
| Description | |
| Found date | |
| Found by | |
| Status | |
| Problem | |
| Severity | |
| Fix/Workaround | |
| Fixed By | |
| Fixed Date |
Description of severity codes |
|
| Fatal | Program or computer locks up or crashes, reboot may be required. Program or computer does not crash but data is definitely damaged. |
| Severe | Program functionality or data integrity is compromised. GPF or other fault occurs that does not cause the program or computer to crash. |
| Moderate | Program behaves in an inconsistent or unexpected manner. Incorrect data appears in a field or fields or not refreshed even though the underlying data is correct. |
| Minor | Merely annoying or aesthetically unpleasant. Program functions normally. |