ODAC supports Oracle 7.3 and Oracle 8. Is ODAC to be used in previous Oracle versions?
In order to use ODAC on Oracle's previous version, you need to install Oracle 7.3 and Oracle 8 SQL-Net2.3 on the client. Sorry, if you have already installed other versions * SQL-Net, all settings (including database alias) will be lost. To save these settings, we recommend that you reinstall (installation) The Oracle call interface contained in Oracle 7.3 to serve as an alternative to Oracle * SQL-Net. Such changes will not affect any other installed settings, which is necessary to implement ODAC functionality.
In order to quickly rewrite the project created with BDE DAC as ODAC application project, what must I do? Should be performed in the following steps: The Following Steps Should Be Made:
Delete all TSESSION components.
Execute the following modifications:
Change the TDATABASE control to Torasession
Change the TQuery control to ToraQuery
Change the TSTOREDPROC control to ToraStoredProc
Change the TTable control to Toratable. If you use UpdateObject, you must change ToraQuery, write in its SQL property:
Select * from
For TupdateSQL controls, we write its deletesql, insertsql, and ModifySQL content to the SQLDelete, Sqlinsert, SQLModify, and SQLModify. A part of a big project has been put into operation, can you use ODAC to create a new module, make BDE DAC and ODAC work together in this way?
There is no limit to using ODAC and BDE DAC in the same project. However, we have a requirement: ODAC and BDE DAC must use different sessions (sessions) because of the following:
ODAC and BDE DAC cannot share the same transaction
Perhaps, the number of sessions must be added to get support for the server.
In order to avoid this situation, TBDESession components should be added to connect to Oracle.
What does the call debugging and SQL operation execution provided by ODAC and the PL-SQL refers to?
ODAC provides two additional debugging methods: design and running when designing. SQL Designer, all ODAC datasets of component editing are inherited in it, allowing debugging servers when designing:
Execute SQL queries and results demonstrations and design queries
The PL-SQL block is initialized with parameters and the internal process of tracking the PL-SQL block execution after the execution is returned. The breakpoint is set to return the settings and change values of the variable when the PL-SQL is executed.
The DEBUG attribute in the ODAC data set is used to debug during the running period. If this property of the ODAC dataset is set to True, the query or block code and parameter value information will be sampled when the query or PL-SQL block is executed.
What is the difference between ToraQuery, TSMARTQUERY, and TORATABLE? All of these components are inherited from TDataSet and have some features:
ToraQuery is to perform data queries and edit the most common methods, you can decide any SQL operation or execute the record insertion, update, and delete operation of the PL-SQL block. In design, you can use ToraQueryEditor's SQL Builder to help you generate a DML operation statement, or use a stored procedure generator to generate a stored procedure. ToraQuery implements all the features of the ODAC dataset. TsmartQuery and Toratable can reduce programming design time. TsmartQuery saves you to perform data updates and generate DML operations. Generally, most tables in your application should use it.
TORATABLE fully supports data queries and updated SQL operations and local tables. Only tables or view names are required to be filled in.
"Not complete"
