I don't see why not? By separating the retrieval of the dddw from the main dw
you are acquiring absolute control over these objects. Save the value required
from the CLIECKED event into an instance variable. After the main dw has been
retrieved, use whatever data from the main dw you need AND use the saved data
from the CLICKED event to populate your dddw(s).

If the various rows on the main dddw have different data that is required for
the dddw, and if some rows do not have the same data as other rows, then you
need to get ALL of the data from ALL of the main_dw rows into either the dddw
then FILTER the dddw appropriately.


Olan

-----Original Message-----


Will this solution work if you only have a single dddw that is dynamically
populated in multiple rows. This is my problem. The dddw is filtered
dynamically in the clicked event from the cached ds and then populated the same
on all pertinent rows using the single dddw and filter from the clicked event?
unfortunately not all rows will meet the same changed requirements as the
row(filter will not meet all row requirements)

--- On Thu, 7/16/09, Olan Knight <Olan.Knight@...> wrote:


Mike -

It sounds like you have all of the dddw set to auto-retrieve.
Separate the retrieval of the primary dw from the dddw retrievals:

1. Put the various dddw retrievals in the "pfc_populatedddw" event,
handling each dddw as required
2. Remove the auto-retrieve property from the dddws
3. In the dw.pfc_retrieve event, set redraw to false and retrieve the
primary dw
4. Call the "pfc_populatedddw" event after the retrieval
5. set redraw to TRUE


OLAN

-----Original Message-----

Hi all,
I have a problem that is occuring as the result of a current rewrite
of our existing system. Pretty complicated. using pb 9.02, Oracle, win
xp professional.
I have a datawindow that contains multiple dddw's that are created
dynamically on retrieve. In the old system the arguments being passed
into the dw were not directly tied to the dddw and displayed the same in
all the dymanic dddw's created. The new system ties the dddw directly
to 1,2 or 3 unique numbers that are being passed into the dw. as a
result, when you filter a dddw with a specific argument in the clicked
event: using Gnv_app.inv_ dwcache.of_ retrieveCachedDa ta(this, 'item_id',
ls_filter), the other dddw's will display the ID instead of the
description, because the description is no longer valid for those
dynamic dddw's. Is there a way to stop all other dddw's from
retrieving(protect those associated rows)and will protect the
descritpion from defaulting to the data ID instead of the previous valid
description field? I know the code should be placed in an event after
the itemchanged of the dw? Thanks in advance for all your help, this is
an excellent newsgroup bot
h for response time and quality of answers I've received in the past.

This e-mail and any attachments are confidential and may also be legally
privileged and/or copyright material of Intec Telecom Systems PLC (or its
affiliated companies). If you are not an intended or authorised recipient
of this e-mail or have received it in error, please delete it immediately
and notify the sender by e-mail. In such a case, reading, reproducing,
printing or further dissemination of this e-mail or its contents is strictly
prohibited and may be unlawful.
Intec Telecom Systems PLC does not represent or warrant that an attachment
hereto is free from computer viruses or other defects. The opinions
expressed in this e-mail and any attachments may be those of the author and
are not necessarily those of Intec Telecom Systems PLC.