FRD is nice thing to work. can you also provide more detail on pl/sql profiler and dbms_support package...
Shuja
"Jamadagni, Rajendra" wrote:
Connor,
Forms is dumb ... I mean it doesn't think it is important to use dbms_application info, you have to do it manually. The statistics parameter ... gosh .. never got it to work right against 7x, 8x and 9x ...
For my developers, I tell them use use,
* FRD (Forms Runtime Diagnostics) if they want to know which built-in is blowing up the form ...
FRD also has different options and you can also use trace diagnostics with forms.
* PL/SQL Profiler (to see where they spend lot of time writing redundant code)
* dbms_support.start_trace for SQL performance problems.So, there are different techniques for different problems.
Raj
______________________________________________________
Rajendra Jamadagni MIS, ESPN Inc.
Rajendra dot Jamadagni at ESPN dot com
Any opinion expressed here is personal and doesn't reflect that of ESPN Inc.
QOTD: Any clod can have facts, but having an opinion is an art!-----Original Message-----
From: Connor McDonald [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 28, 2003 6:29 PM
To: Multiple recipients of list ORACLE-L
Subject: Re: tuning forms/reports applicationthere is a stats=yes (or similar) parameter which
creates a trace file for a form execution which can
then be used to check sql performance (the most common
cause of 'slow' forms).i haven't checked, but forms by default might pop some
things into module/action columns which you could see
in v$session and v$sql. if forms is not doing it by
default, then its a very good practice to start doing
this yourself (see: dbms_application_info)hth
connor
