Lock-procedure using headstart for designer

Question

When deleteing a record from a form that has been generated using
designer (headstart installed), I get the error "FRM - 40700 No
such procedure: LOCK-PROCEDURE". I looked through the
headstart library QMSLIB50.pll and found three reference to this
procedure but can not find the actual procedure. What am I
missing?
Thanks
Alan Schif
null

Answer 1

Alan,
I'm not sure what the problem could be. I have tried this myself
and have no problem doing the delete (or updates). Note: I'm on
Form Builder 6.0. You don't mention which version you are using.
Assumptions:
You have created a TAPI for your base table.
You have created a MAPI for your module.
You have set the module component to Data Target Type = PL/SQL
Procedure.
You have generated the module.
If you look at the form in Form Builder, the block should have
DML Data Target Type = Procedure and DML Data Target Name = null
or a package.procedure name. The insert, update, delete and lock
procedures should be filled in with the appropriate procedure
names. You should have a block level ON-LOCK trigger that
contains a call to qms$event_data_block('ON-LOCK') in
qmsevh50.pll. (Designer should do all this for you.)
In qmsevh50.pll, qms$event_data_block should contain a call to
qms$record.on_lock in qmslib50.pll. This procedure should check
the dml data target name and if it is null or contains a
package.procedure name, it should call the execute_trigger
procedure to execute the LOCK-PROCEDURE trigger.
This procedure is automatically generated by Form Builder at
runtime. The Form Builder on-line help has the following to say
(under 'Lock-Procedure Trigger'). "Automatically created by Form
Builder when the lock data source is a stored procedure. This
trigger is called when a lock operation is necessary. Think of
this as an ON-LOCK trigger that is called by the system instead
of doing default lock operations. Do not modify this trigger."
This is only valid when the dml target type is Procedure. If the
dml target type is table, the dml target name should contain the
name of a table. Oh, I just thought of something. Are you
by any chance using schema.table_name in your blocks? If so,
this would cause the problem you describe. See the note in the
qms$record.on_lock procedure in qmslib50.pll. Ideally, the code
should simply check the dml target type for Procedure. However,
due to a forms bug (655567), we can't do this. So, we used a
work-around. We check for the presence of a '.' in the name
assuming that if a '.' is present, it must be
'package.procedure'. However, it could also be 'schema.table'.
If this is the case, you might want to consider using the new
'alter session set current schema' option available in Oracle
8.x. Rather than referencing the schema in each block, you add a
line to your application library to set the schema when the user
first logs on. See the Headstart Template Package User Guide,
chapter 8 (Runtime Environment), 'Alter Session Current Schema'.
I hope this info helps you to resolve your problem.
Best Regards,
Lauri
Alan Schif (guest) wrote:
: When deleteing a record from a form that has been generated
using
: designer (headstart installed), I get the error "FRM - 40700
No
: such procedure: LOCK-PROCEDURE". I looked through the
: headstart library QMSLIB50.pll and found three reference to
this
: procedure but can not find the actual procedure. What am I
: missing?
: Thanks
: Alan Schif
null