Home DADE

Linking DADE and Standard Pipelines via Code

edited November 2004 in DADE
Hi,

I have a couple of questions regarding linking a DADE pipeline with a
standard pipeline (or two DADE pipelines) via code. I have looked at a
couple of examples (see links below) and they both work great and have
helped tremendously however there are a few items that I need some
clarification.

http://www.digital-metaphors.com/tips/LinkDADEPipeToStandardPipe.zip
http://www.digital-metaphors.com/tips/LinkEditSQLDatviews.zip

Both examples indicated that the key to making this work is that the lookup
data must be ordered properly or the lookup could fail. The lookup data
must be ordered the same as the master dataview, plus ordered by the fields
used to establish the link.

In the example LinkEditSQLDataview the masterview (DADE Customer pipeline)
is not ordered at all and the lookup data (DADE Orders pipeline) is ordered
by CustNo, OrderNo. This does not seem to meet the criteria of the above
statement in that the lookup data must be ordered the same as the master
dataview.

#1: Is it required that that the lookup data be ordered the same as the
master dataview or is the key that the lookup data be ordered by the fields
establishing the link?

#2: Does the masterview have to have any special ordering to make this work
(i.e. be ordered by the fields establising the link)?

The scenario that I have is that I have a DADE pipeline (master pipeline)
that is being linked with a standard pipeline (detail pipeline) in an
end-user reporting enviroment. The detail pipeline is ordered by the field
LoanNo which is the field establishing the link. The master pipeline is
ordered by the fields LoanFundName, LoanNo. This seems to work fine however
I am concerned that should the user changed the ordering of the master
pipeline that there is potential for the report to fail. For example, in
some scenarios the user want to order master pipeline by LoanFundName,
BusinessName, LoanNo.

#3: Will changing the ordering of the master pipeline as in the above
example cause the report to potentially fail?

When you link two pipelines in DADE you have two options as to how the
linking behaves "1 - Include only those records..." or "2 - Include all
records...".

#4: Is it possible when establishing the link between two pipelines via
code to specify how the linking behaves? In both examples provided the
linking code seems to handle the first behavour above ("1 - Included only
those records...").

#5: In both examples provided the object lLink: TppMasterFieldLink gets
created but never seems to get destroyed. Does this field automatically get
destroyed or should it be destroyed in code?

Thanks in advance for your assistance.

Sincerely,
Scott Rowat

Comments

This discussion has been closed.