1. How do I make a compiled form file to an .exe application.
2. I want to use Oracle Developer under database SQL server. I've set datasource by using ODBC for SQL Server database and connected successfully by using SQL* Plus, but when I log on to Forms, the error appears and no table can be seen.
Would you please help me resolve these problems? On a Unix system, you would use make utility. The examples below...
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
are for Unix, although similar capabilities exist on Windows platforms (and probably have a utility make or makefile) with very similar syntax. You need to check your documentation for the OCI (Oracle Call Interface) which has pre-compilers for C, COBOL, Fortran, etc., for how to wrap the form with a program interface. Unix examples are given below in the Appendix.
Using Oracle Developer under SQL Server data brings up an interesting question. While it can be done, I would question the reasons that you are doing so. Take a look at your application architecture, and verify that you are interpreting the business needs appropriately. You may want to consider conversion of the database to Oracle, or the forms to some other application, depending on the long-term goals of the organization. That being said, yes, you certainly can do what you want to do. You will want to look in detail at the documentation on the Oracle Client Adapter, with respect to ODBC.
Developer 2000 form builder requires that certain views are present in the data source in order to properly access data dictionary information. Forms Builder uses this information to display lists of tables, columns, views, etc. If these views are not present, you will not be able to see the lists of tables, views, etc. However, you can still use the objects from that data source by physically typing the names of those objects.
Forms Builder comes with re-entry mode Data Block Wizard to create blocks based on tables, views, synonyms, etc. When you connect to an Oracle data source by default data dictionary contains all the tables and views that are required by the Data Block Wizard. And, therefore, the wizard would be able to retrieve all the tables/views, etc., available to the person who logs on.
However, when connecting to non-Oracle data sources like SQL Server, MS Access, DB2 etc., Data Block Wizard will not be able to retrieve the available tables for the users. The Oracle Open Client Adapter provides a number of scripts for generating data dictionary views/tables on some non-Oracle databases.
APPENDIX ( Make EXE)
You use a program from an Oracle pre-compiler (ProC, Fortran, COBOL or whatever) to create an executable program.
The program proc.mk is a generic linking tool. It is designed to link together programs that are in multiple modules without modification. The makefile itself is found in $ORACLE_HOME/proc/demo, along with sample programs. In order to use it for a single module, you would use make -f proc.mk EXE=
unix$ make -f proc20.mk EXE=my_prog OBJS=my_prog.o/u03/oracle7.1/bin/proc iname=my_prog.pc
General suffix rule to build executables from .pc and .c files.
Usage: make -f proc.mk USERID=
For example, to build an executable from a Pro*C source file named 'abc.pc' using scott/tiger for the ORACLE account name. The make command line will be:
make -f proc.mk USERID=scott/tiger abc
Note: scott/tiger is the default account/password, so that you could also use the following command line:
make -f proc.mk abc
The executable will be named 'abc'.
So you can define the EXE macro to be the name of the executable, and the OBJS macro to be the object files us.
Related Q&A from Carol Francum
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.