TOOLLBAR ERROR FM-41003

Dicas do Oracle Forms Builder - Blocos, Itens, LOV, Canvas, Triggers, comandos, PLL, d2kwutil, FMB, Alert, menus, etc
Post Reply
Pablo
Rank: DBA Júnior
Rank: DBA Júnior
Posts: 190
Joined: Fri, 27 Oct 2006 11:12 am
Location: 88350000
Pablo

Hello friends, I use Forms 6i on BD 11G.
Good, I created a font with a custom toolbar.
On the new screens I create, I refer to the toolbar with my source.

The problem is in the toolbar, because when I click on the Refer button (the button command is: do_key(ENTER_QUERY) It shows the error FRM-41003 This happens with almost all the Buttons created, only save, exit and delete is that work correctly. Gives the impression that by clicking the button it runs the command without taking into account the block in which the cursor is.
Have you passed this?

Hugs
spernega
Rank: DBA Pleno
Rank: DBA Pleno
Posts: 232
Joined: Tue, 19 Jun 2007 2:12 pm
Location: São Paulo - SP

Good afternoon Pablo,

take a look at the topic FRM-41003 - This function cannot be performed here here in the forum.
See if it helps.
Pablo
Rank: DBA Júnior
Rank: DBA Júnior
Posts: 190
Joined: Fri, 27 Oct 2006 11:12 am
Location: 88350000
Pablo

Hello, sorry for the delay, but I had to move away for reasons of disease.

Dude, I had already looked at this topic, but it did not help at all. The message is the same, the problem is that I want to use the Toolbar ... and the error happens when I click the query button (for example). The buttons for the block do not work, only the buttons for Forms.
Example: I want to jump to the next line of the block ... This button does not work.
I want to save the block, the works button.

The use button do_key("comando")

Hugs
spernega
Rank: DBA Pleno
Rank: DBA Pleno
Posts: 232
Joined: Tue, 19 Jun 2007 2:12 pm
Location: São Paulo - SP

I hope you are better ...

Are you using this call in the Toolbar block?

Select all

do_key(get_item_property(:system.trigger_item,item_name));
If yes, try to change to a trigger at the level of item with the command, only to test.
Pablo
Rank: DBA Júnior
Rank: DBA Júnior
Posts: 190
Joined: Fri, 27 Oct 2006 11:12 am
Location: 88350000
Pablo

Oops ... I'm better ... thanks ...
That's right, I'm using the call on the block. I made the change according to your guidance ,,, but it did not work .. it will be the impression that when you click the button the forms does not understand that the command is for the block where the cursor is.
spernega
Rank: DBA Pleno
Rank: DBA Pleno
Posts: 232
Joined: Tue, 19 Jun 2007 2:12 pm
Location: São Paulo - SP

Pablo,

puts a message on the trigger of the

Select all

message(:system.cursor_block); 
pause;
only to make sure that block is the cursor.

Another thing, see if in the properties of the button it is with the Navigable Keyboard property, Mouse Navigate marked as "no".
Pablo
Rank: DBA Júnior
Rank: DBA Júnior
Posts: 190
Joined: Fri, 27 Oct 2006 11:12 am
Location: 88350000
Pablo

Dude ... that's right ... the buttons were with the option of navigable keyboard and navigable mouse like yes ... and should be like no.

Wow ... Thank you again.

Hugs
Post Reply
  • Information
  • Who is online

    Users browsing this forum: No registered users and 6 guests