Chapter Contents |
Previous |
Next |
SAS/ACCESS Interface to CA-DATACOM/DB: Reference |
When you update an access descriptor, the view descriptors based on this access descriptor are not updated automatically. You must re-create or update any view descriptors that you want to reflect the changes made to the access descriptor. That is, for some updates (such as dropping a field), the view descriptors are still valid, but they do not reflect the changes made in the access descriptor. In other situations (for example, if you edited the access descriptor to use a different userid or to add a password), the view descriptors would no longer be valid. A valid descriptor file can also be made useless by an update. For example, if an update to an access descriptor drops two of the four fields defined in a view descriptor, you may want to update or delete the view descriptor.
The following example updates access descriptor MYLIB.CUSTS to drop additional fields. The VLIB.USACUSTS and VLIB.CUSTADD view descriptors remain valid, however, you may want to update them to select new fields to replace those dropped as a result of the update.
proc access dbms=datacom; update mylib.custs.access; drop 3 7; list all; run;
The statements are described below.
proc access
dbms=datacom;
update mylib.custs.access;
drop 3 7;
list all;
run;
Altering a CA-DATACOM table that has descriptor files defined can also cause these files to be out of date or invalid. If you add a field to a table, an access descriptor is still valid. However, if you delete a field or change its characteristics and that field is used in a view descriptor, the view will fail when executed. For more information, see How Changing the CA-DATADICTIONARY Database Affects Descriptor Files.
Chapter Contents |
Previous |
Next |
Top of Page |
Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.