Home » Developer & Programmer » Forms » Primary Key Item Behavior
Primary Key Item Behavior [message #634665] Thu, 12 March 2015 12:57 Go to next message
elmousa68
Messages: 20
Registered: September 2012
Junior Member
I have a database block based on the following table:

SQL> desc jov;

Name Null? Type

----------------------------------------- -------- ----------------------------

JOVID NOT NULL NUMBER(6)

COUNTRY VARCHAR2(3)

CITYK VARCHAR2(9)

NAME1 NOT NULL VARCHAR2(18)

NAME2 VARCHAR2(18)

NAME3 VARCHAR2(18)

NAME4 VARCHAR2(18)

BIRTHDT DATE

STREET VARCHAR2(70)

HOMPHON VARCHAR2(10)

QUALIF VARCHAR2(1)

QUALIFSTAT VARCHAR2(1)

NATCOD VARCHAR2(3)

NATNO VARCHAR2(10)

SEX NOT NULL NUMBER(1)

MOTHNAME1 VARCHAR2(18)

MOTHNAME2 VARCHAR2(18)

MOTHNAME3 VARCHAR2(18)

MOTHNAME4 VARCHAR2(18)

PASSNO VARCHAR2(20)

BLODTYPE VARCHAR2(3)

CITY VARCHAR2(9)

POBOXNO VARCHAR2(10)

MOTHNATCOD VARCHAR2(3)

MOTHNATNO VARCHAR2(10)

FAMBOOKNO VARCHAR2(20)

ENTRYDATE DATE

SOCSTATUS NUMBER(1)

REL NUMBER(1)

SUBCATK VARCHAR2(Cool

USERID VARCHAR2(5)

The primary key in the table is the field jovid.

When the form runs, the item which is based on jovid acts as follows:

in insert/update mode does not accept the focus, i.e mouse cursor does not enter item.

in enter query mode, item accepts the focus and mouse cursor enters the item.

There are other items on the form, e.g natno, which have the exact properties as jovid but act as expected. i.e they accept the focus in both modes.

What is more, is that when I delete the said item (jovid) and create a new one (with the same name) with default properties, I have same strange behavior.

I note here that this happens only when item name is jovid... if I create an item and name it xyz then I have normal behavior!

Any help is appreciated.

Please note we are using Forms 10g connected to an Oracle 11g database.
Re: Primary Key Item Behavior [message #634675 is a reply to message #634665] Fri, 13 March 2015 01:17 Go to previous message
Littlefoot
Messages: 21580
Registered: June 2005
Location: Croatia, Europe
Senior Member
Account Moderator
As far as I can tell, there's nothing special in JOVID (so that Oracle would refuse entering that item).
  • Is this a brand new form? Did you create it? Using a data block wizard, perhaps?
  • Are there any triggers which modify JOVID item's properties (with SET_ITEM_PROPERTY)?
  • Try to create WHEN-NEW-FORM-INSTANCE trigger (if you don't have it already), set a breakpoint in there and run a form in debug mode. Follow its execution; maybe you'll find a culprit.
Previous Topic: Export data into Excel Template
Next Topic: show error when run form
Goto Forum:
  


Current Time: Fri Aug 14 21:11:59 CDT 2020