VisualAge saves queries, stored procedures, and connection specifications in access sets. An access set can be packaged with your application, much like the classes that define your visual and nonvisual parts. An access set can hold many queries, stored procedures, and connection specifications, and can be shared by different applications.
To define an access set:
The new access set is added to the list of parts for your application.
If you use only one database manager, you can use the same access set for storing all of the queries, stored procedures, and connection specifications in an application. If you use more than one database manager, such as DB2 and SQL Server, create an access set for each database manager. Though using separate access sets is not a requirement, it helps you to determine appropriate prerequisites when you package your application. VisualAge attempts to maintain prerequisites according to the connection specifications defined in an application.