Use Create Oracle Application to adapt the Access front-end application to operate using the data you migrated to Oracle.
Adapted database file location: Type the location where you wish to save the Access database file that has been adapted to operate using Oracle data, or use Browse to display a standard file open dialog box.
Save Password Locally: You can choose to save the Oracle login information on the local PC so that Access will not prompt for it when the application is subsequently started.
User/Owner: Directs Scriptoria to search for Oracle tables/views that correspond to Access tables/queries in the currently selected User/Owner (set/shown on the Options page) . Access tables with no corresponding Oracle table are included when using the Create Oracle Application feature.
In addition to linking to associated Oracle tables and binding table and field names to retain the identifiers that your application objects (forms, reports, modules, etc.) expect, the linked Oracle table inherits all Access table and field properties, including Input Mask, Lookup, Format, Description, Allow Zero Length (see note), et al.
Notes:
The adapted database cannot be used with Scriptoria. The original database should always be used to make design modifications to the migrated Oracle database. To ensure proper application operation, repeat the Create Oracle Application process after completing any design modifications.
When the Query Translation module is installed, see Client-Server Bind Options.
There is an important DataDirect work-around that must be implemented before generating new Access applications that operate with Oracle.