thanks to all for the help.
I kept the separate cache.
 
 
(Still question comes to mind ,was there a major issue in giving read access to the block buffer, it would save lot of validation code)
 
Regards
Sameer
-----Original Message-----
From: Duncan Mills [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 30, 2003 1:59 PM
To: Multiple recipients of list ODTUG-DEV2K-L
Subject: Re: forms6i question

Nope - keeping a separate cache in a PL/SQL table / RG  is the only way.

Regards
 
Duncan Mills
Senior Principal Product Manager
Oracle Application Development Tools
 
----- Original Message -----
Sent: Thursday, January 30, 2003 5:09 AM
Subject: forms6i question

Hi All ,
Can anyone tell me if there is any handle or cursor to a block record buffer
,which I can access in forms6i.
my requirement is to restrict user from entering duplicate records in the
block while inserting'em (but before saving them).
As soon as user enters the row  TAB's out I want to check it with  values in
the other row in WHEN-VALIDATE-RECORD trigger
(Note that rows are not yet stored in the database)

I have implemented this using PL-SQL table/Record Group by replicating data
in the block with PL/SQL table,
(but it requires coding in many triggers)
I was wondering if there is more simple and efficient solution to this.

Thanks
Sam
--
Join us at Loews Miami Beach, Florida on June 22-27, 2003 for our best
ODTUG Conference yet!  Details and registration at:  http://www.odtug.com
--
Author: Sameer Ghadge
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ODTUG-DEV2K-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Reply via email to