When the Query Translation module is installed and Scriptoria finds Oracle views or procedures for the current user that match Access queries, the Client-Server page is shown on the Generate Access/Oracle Application form.
The following disposition options specify which Oracle objects will be used with the new Access/Oracle application. The default settings preserve the functionality of the original Access front-end.
By default, MS-Access queries are based on ODBC linked tables that inherit all properties of the original tables. Queries that were updatable in the original application are also updatable with some exceptions (ODBC linked tables must have a primary key to be updatable).
This option instructs Scriptoria not to create pass-through queries.
This option instructs Scriptoria to create an additional pass-through queries when corresponding Oracle views (or Crosstab procedures) are found for the current user. The original Access query, now linked to corresponding Oracle tables, remains the default query used by the application. You can set other options for individual queries using the Assign Individual QueryDefs facility..
Use this option to create new pass-through queries and to replace the original Access queries with the new pass-through ones.
This option creates new pass-through queries and replaces the original after it is renamed with a suffix of (LQ).
The same options available for selection queries also apply to action queries. Action queries also include the following option:
It is often desirable to create Oracle scripts that call procedures generated for MakeTable and Delete queries. To prevent Access users from inadvertent updates, set this option to "Yes" so that MakeTable and Delete queries are omitted from the converted application. (See Bulk Updates).
When set to "Yes," Scriptoria substitutes functionally equivalent pass-through queries (when available) for all report RecordSource and control RowSource properties.