Re: Display-only items
Date: 1998/03/19
Message-ID: <6erii5$f4k_at_info.csufresno.edu>#1/1
In article <1998Mar18.151839.10049_at_vmsmail.gov.bc.ca>, Mark Cudmore <mcudmore_at_kamloops.env.gov.bc.ca> wrote:
> I want to create an item on a form that is visible, but I don't want
> the user to navigate to it with their mouse. The only way I can do
> this is to set the ENABLED property to False, but this greys out the
> item, making it hard for the user to read it. What should I do?
Change the item type from Text Item to Display Item. But this only works if you don't need a format mask, since Display Items do not have a format mask (I wonder why Oracle did that).
I have also heard that putting a when-new-item-instance trigger on the item with the command: Raise Form_Trigger_Failure will prevent mouse navigation, but I haven't tried it. You could also do a go_item in the when-new-item-instance trigger.
[Quoted] But my question is this: What is wrong with allowing the user to click on the item? We have lots of display-only fields where the user can click on them, and the field is automatically highlighted (background becomes yellow). I like the feature... if user A is talking with user B about the field, it is sort of user-friendly to allow the mouse click to bring the visual focus to the item being discussed... wouldn't you agree?
We have an individual here who insisted on preventing mouse-click navigation to display-only items, and in the places where that logic was attempted, it has just caused additional problems.
Regards,
Steve Cosner
http://members.aol.com/stevec5088
Downloadable Quick Access utility form: Display and update any table. Received on Thu Mar 19 1998 - 00:00:00 CET