FRM-41092 No records in block ...
iulian
I have an application which ran okay with Forms 6 but when I try it in Forms
6i I get an error FRM-41092 No records in block <a_block_name> The block
<a_block_name> isn't a database one and contains only command controls
(buttons, display items, etc). I don't understand what might be error.
Thanks for your time.
iulian
Alan Mills
use any of the buttons in it. If your display item(s) show some details
then you will have at least one record and so no problems that I can
foresee. What worries me is that it seemingly worked before. Arer you sure
you are performing the same test?
"iulian" <4s...@mail.com> wrote in message
news:b3Lv9.103083$mxk1....@news04.bloor.is.net.cable.rogers.com...
iulian
What do you mean by having one record in the block?
Like I said there is not a database block (Database Data Block = No) and it
did work before. Actually there are 2 more blocks in the module that aren't
database typed and I get the message only for this particular block. I even
select all three blocks and check for the properties and the only different
one is Name.
I developed this application using Forms 6 and it worked,; now after I
install Forms 6i no more working app. I must say it's a bit frustrating...
iulian
"Alan Mills" <Alan....@nospamservices.fujitsu.com> wrote in message
news:apoa60$2pe2$1...@news.icl.se...
Alan Mills
block. Being a da5tabase blocvk means to Forms 'shall I generate DML
statements at commit time?'. The block can still hold data.
In order to help determine the exact cause, we'll need a little more
information. What buitling is being called to cause the error to appear, or
what button are you pressing and from which field in which block etc etc.
Any triggers firing as a result of that key press. At the end of the day it
will be a line of PL/SQL or a stanadrd builting causing the error, whcih one
is it?
Also, you didn;t answer the question of whether there is a record in the
block or not. Try navigating to the record before you do whatever cause the
problem. This will cause a 'new' record to be created in the block so the
block will then have at least one record.
"iulian" <4s...@mail.com> wrote in message
news:ZfRv9.105904$mxk1....@news04.bloor.is.net.cable.rogers.com...
iulian
elsewhere. I eliminated a small bug in a procedure on the server side and
everything works fine.
Pretty annoying. 'cause the other blocks were ok and this particular one
wasn't even if they all are alike, speaking about their properties. And I
didn't have any clues where to look into.
I did want to answer your question but I think I didn't get exactly what did
you mean. So I decide to list the properties. For all my control blocks
(block containing only non database items) I only set these ones:
Database Data Block = No
Query Data Source Type = No
DML Data Target Type = None
and that's it.
I leave the rest of them as default. I list for you the properties in the
Records Group.
Current Record Visual... = <Null>
Query Array Size = 0
Numebr of Records Buffered = 0
Numebr of Records Displayed = 1
Query All Records = No
Record Orientation = Vertical
Single Record = Yes
I guess these are the default values, and all my control blocks have'em like
above.
The error showed up before my form being displayed but after login time.
What pissed me off it was why the other blocks seemed to work okay and the
trouble one no.
Anyway I'm half happy that now it's working, cause I don't want this happen
again, but what do you know...
If you want to make more comments feel free, I will learn from it, but if
you don't no problem.
Thanks again for your answers.
iulian
"Alan Mills" <Alan....@nospamservices.fujitsu.com> wrote in message
news:app07e$2r7$1...@news.icl.se...