Oracle-L: Re: Designer2000 & LOV generation.

From: James Manoharan <Manoharan_James/NUC_SUSQ1_at_PAPL.COM>
Date: Tue, 5 Mar 1996 10:10:44 -0500
Message-Id: <9603051532.AA30616@alice.jcc.com>

>>>> From my experience in the LOV , i can give something to you.

From: ORACLE-L; vmt043
To: ORACLE-L
Subject: Designer2000 & LOV generation. Date: Tuesday, March 05, 1996 3:16AM

<<File Attachment: DESIGNER.TXT>>
We have some questions about how Des2K generates LOVs in Forms modules:

Environment: Windows for WorkGroups 3.1.1, Designer2000 V1.0.7.1.0, Form= s=20
4.5

Question 1:

How does Des2K determine which column the LOV button is attached to? >>>>>>
>>>>>>>

If you want to attach LOV button for a particular column do the following steps.

Go to Prefernece navigator and select the module expand the modules up to Detail columns usages. set the LOVBUT = Y perference (col2) for the column.

ex. +modules

       + detaile table usages
          + detaile column usages
            + col1
            + col2

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

What exactly does the "lookup item" property do in the generate process?=

>>>>> This will tell you that this field have a LOV.

           so, that you can use your LOV key ie. F9
          If the "lookup item" is not set true , you can't use LOV.
--------------------------------------------------------

Examples:
We have a base table with a foreign key code to the lookup table. (* =3D primary key)

Base table:

     id*
     foreign_key_cd

Lookup table:
     cd*
     descriptor_name (descriptor sequence 1)
     other_descriptor_column  (descriptor sequence 2)

Example A:
We want to display the base table code and the lookup descriptor column.=

Base.foreign_key_cd is displayed.
Lookup.cd is not displayed.
Lookup.descriptor_name is displayed.
We want the LOV button on Base.foreign_key_cd but the generator attaches= it=20
to lookup.descriptor_name.

>>>>>>>>>>>>>>>>

For this case , set "lookupitem" = TRUE for basetable.foreign_key_cd and set "display in lov" = TRUE for lookup table.cd,lookup table.name and as i said above go to perfernce navigator set the column level LOVBUT perference
= 'Y'.

Example B:
Sometimes we only want to display two columns from the lookup table. Base.foreign_key_cd is not displayed.

Lookup.cd is not displayed.
Lookup.descriptor_name is displayed.
Lookup.other_descriptor_column is displayed.

We want the LOV button on Lookup.descriptor_name but the generator attac= hes=20
it to lookup.other_descriptor_column.
>>>>

Question 2:

How does Des2K decide the display order of the columns within the LOV? It is not using the order of the items from the detailed column usages. It is not using the display order from the table definition either. The sort order is okay, but the display order is inconsistent.

We are well aware that all these items can be changed in Forms Designer=20=

after the form is generated, but we would like to be able to generate th= e=20
forms properly in the first place.

Since the LOV button is sometimes attached to the fields that we want it= to=20
be attached to, we are wondering how we can always make it work as we=92= d like=20
it to.

>>>>>>>>>>>>>
no idea, but for me its displaying in the order.

Thank you for your help.

Jane Taylor
Department of Transportation
Government of New Brunswick
VMT043_at_GOV.NB.CA

.......................................................................

Item Subject: WINMAIL.DAT
Couldn't convert Microsoft Mail Message Data item to text at a gateway. Received on Tue Mar 05 1996 - 10:32:14 CST