Table Procedure Examples, Design, and Use › Access Methods for Selected Records › Unique Access Strategies for Entry, Path, and Auxiliary Records[ › Modify the Selected Access Method

Modify the Selected Access Method

Sometimes the selected access method does not perform the most "correct" method for your database structure. You can change the table procedure code to reflect your understanding of the database design. For example:

• The auxiliary record is CALC, but the unique keys for that record type contain more than the CALC key fields. This condition makes Quick Bridge perform an area sweep. You could enhance the table procedure code to perform OBTAIN CALC DUPLICATE processing which could be more efficient than an area sweep.
• The auxiliary record is not CALC, but is owned by a CALC record. You could include additional columns in the CREATE TABLE PROCEDURE and table procedure code to support the foreign key to that auxiliary record. Then add the required code to return the data in SELECT processing, and the required code to perform UPDATE processing.