0945-0946

Previous | Table of Contents | Next

Page 945

This interface is recommended over building user exits because libraries are only linked in as needed, and thus the form modules can be smaller. Additionally, user exits require that the Oracle Forms runtime designer be recompiled and that all forms run the version of the tools with the embedded user exit. As a result, user exits tend to require more resources than might be needed for each form.

Summary

This chapter shows how you can use the Oracle Developer/2000 tools to integrate with each other, as well as with non-Oracle applications and subprograms. As one of the key features of Oracle Corporation's concept of open enterprise computing, Developer/2000 integration is highly useful for state-of-the-art powerful applications.

One thing to note in using these features is the fact that all these tools demand a large amount of resources. When you combine multiple application modules and tools, the limited resources of a PC are quickly consumed, resulting in applications that perform slowly or not at all.

I am by no means attempting to dissuade anyone from using the integrated features of these tools. I am just trying to caution you about the pitfalls that you will surely encounter.

Page 946

Previous | Table of Contents | Next