Re: Forms Master-Detail question

I think I laughed at the poor Oracle Support tech that told me this:

Create a dummy (non base table item) and set it's sizes to 0, so it's essentially invisable but navigable.

I think that's ludicrous. But that is my opinion. Unfortunatly, that's about the only way to get around that rediculous problem.

Instead of that work around, what I usually do is tag the field read-only just in case a value larger than will fit on screen happens to be populated there.

Then if the user deems it necessary, they can cursor through the data to see what is there.

In article <715eso$ld6$1_at_nnrp1.dejanews.com>, <cary_at_nams.net> wrote:
>Hello,
>
> I'm working on a very simple form in Developer v2.1 and have the following
>problem. Using the Data Block Wizard, I have created a form containing 2
>blocks (based on database views) in a master-detail relationship. I want to
>set up the detail block so that its single item (5-line text item or display
>item) only displays information - no inserting, no updating, no access
>whatsoever by an end-user. If I set up the detail block item to be a display
>item and perform a query on the master block text item at runtime, I get an
>error: FRM-40106: No navigable items in destination block. I get the same
>error if I make the item a text item with the properties Enable=No, Insert
>Allowed=No, Update Allowed=No. However, the error goes away and the block
>updates properly when the detail block item is a text item with Enabled=Yes.
>Functionally, though, this is not what I want. This item should be display
>ONLY. Can someone point out the problem/solution here? Thanks.
>
>
>Cary
>
>-----------== Posted via Deja News, The Discussion Network ==----------
>http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own

--
(: Joe Brown :)				      joe_at_apache.dtcc.edu
I believe Wine is going to be great if it ever gets finished. . .
I believe Linux _is_ great even though it's not finished! ! !
I believe you have my address.  :-)