Formatting a Startup File
When you format a startup file, each keyword must end with a colon. The generic formats are:
Depending on your company’s security procedures, you can display a complete or edited list of users and tables when you start SQR Production Reporting Studio. Use the keywords in the following table to show or hide users and tables.
Table 40. User Name and Table Settings in the Startup File
Keywords | Description |
|---|
Hide_User | Takes database.user names as its arguments. For ORACLE, specify user. The specified users do not appear in the list of available users. SQR Production Reporting Studio does not check the validity of the user name. Example: Hide_User: pubs.barry |
Show_User | Takes database.user names as its arguments. For ORACLE, specify user. If you use this command, only the specified user names appear in the list of available users if the users have tables that are accessible. SQR Production Reporting Studio does not check the validity of the user name. Example: Show_User: pubs.gwyn |
Hide_Table | Takes user.table names as its arguments. For SYBASE, specify the complete table name: database.user.table. For ORACLE, specify user.table. The specified table names do not appear in the list of available tables. SQR Production Reporting Studio does not check the validity of the table names. Only the first table name needs to specify the user name. Subsequent tables specified without a user use the preceding user name. Example: Hide_Table: pubs:dbo.authors.titles |
Show_Table | Takes database.user.table names as its arguments. For ORACLE, specify user.table. If you use this command, only the specified table names appear in the list of available tables for the specified user. SQR Production Reporting Studio does not check the validity of the table names. Only the first table name needs to specify the user name. Subsequent tables specified without a user use the preceding user name. Example: Show_Table:pubs.dbo.authors.titles |
As you define user name and table settings in the startup file, observe the following guidelines:
Separate arguments with a tab, space, return, or comma character. For SYBASE, the arguments are not case sensitive. For ORACLE, the arguments are case sensitive.
Follow command names with a colon (:).
You can enter commands in any order, and you can repeat commands.
When you include a list of arguments with commands, you can string the arguments together on one command line. The system includes all arguments separated by commas or spaces until a new command or user name is read. When you enter table names, you must enter the full database.user.table for only the first table or anytime you enter a table name for a user.