• Article Type: General
• Product: Voyager
• Product Version: 8.2.2

Description:
Bug Report Form for Issue 16384-12737
Module(s): Cataloging
Release(s) replicated in: 7.0.2; also 6.1, 7.2.3

Expected results: When saving a large record in Cataloging, it should save regardless of how many 6xx and 7xx fields are in the record.

Actual results: If the record contains 562 or more 6xx and 7xx fields, when the operator tries to save the record, she receives run-time errors and the client closes without saving the record.

Workflow implications: Work can be lost when the client closes, and full, detailed records cannot be saved.

Replication steps:
1. In Cataloging, find a record with 562 or more 6xx and 7xx fields and bring it into the client via Record > Import.
2. Click Save to DB.
3. Receive run-time error 440, sometimes followed by run-time error 65099, and client closes without saving record when you click OK on these error messages.
4. Cut the number of 6xx and 7xx fields to 561. Click Save to DB. Record is saved.

Other information: Similar to Issue 19066, changing some of the fields above to 999 fields allows them to be saved, and can be used as a workaround, though it does affect indexing. Unlike Issue 19066, this is replicated with a large number of 7xx fields, and the number of subfields in each does not seem to impact how many can be saved.

Workaround: Change field tags beyond the first 561 6xx and 7xx fields to 999 fields.

Resolution:
Fixed in Voyager 8.2.2.

• Article last edited: 3/4/2015