[adm2-dev] Filter problem with parent - child SDO relation - Forum - OpenEdge Development - Progress Community

[adm2-dev] Filter problem with parent - child SDO relation

 Forum

[adm2-dev] Filter problem with parent - child SDO relation

  • Hello all,

    I have a problem with the dynamic filter in the ADM2.

    I've not yet circumcised the problem completely but it happens when I want

    to filter on a field in a SDO which is also the foreign field for another SDO.

    Example:

    - SmartWindow

    - SDO Parent

    - SDO Child (linked to parent through a foreign field)

    - Dynfilter

    - Browse Parent (showing records from parent sdo)

    - Browse Child (showing records from child sdo)

    Links are (besides the obvious container links and data links between sdo

    and browse):

    SDO Parent data > SDO Child (with foreign field)

    Dynfilter - filter > SDO Parent (filter on field which is also the

    foreign field for the data link between the two SDO's)

    When I try to create this situation the following happens:

    - The filter field is shown as READ-ONLY so it's impossible to filter on

    - No operator is shown besides the filter field

    - An error message comes up (Entry 2 is out of range) when the window is

    first started. Debugging the adm2 filter.p super procedure shows that this

    error comes in the dataAvailable procedure at the point where foreignvalues

    are processed. Although the SDO has foreign fields, there are no foreign

    values because it's the PARENT of the relation between SDO's.

    It seems that the dynfilter doesn't take into account the fact that the SDO

    that he's filtering on is the PARENT of a foreign field relation, rather

    then the CHILD. I understand that it shouldn't be allowed to filter on a

    foreign field if that field is already supplied by a parent SDO, but in

    this case the SDO on which the filter operates is the PARENT.

    I'm on V9.1C20.

    Can someone explain how to solve this bug?

    Best regards,

    Wim

    _________________________________________________

    Ing. Wilhelmus van der Ham

    WITS - Worldwide IT Solutions sas

    di Wilhelmus van der Ham & C.

    Italian partner for DWP: http://www.dynamicwebclient.info

    via Motrassino, 2

    10078 Venaria-Reale (TO) - Italy

    Internet: http://www.wits.it

    Telephone: +39-011-4527691

    Mobile Phone: +39-335-6877283

    Mobile Fax: +39-335-0-6877283

    To unsubscribe, e-mail: dev-unsubscribe@adm2.possenet.org

    For additional commands, e-mail: dev-help@adm2.possenet.org

  • The ForeignFields property is only used by SDOs that have a parent, so maybe

    you can set it to blank?

    If the ForeignFields is defined because this Window also can be called from

    another Window that adds another SDO as a parent with pass-thru link, then

    you may need to do this conditionally when the DataSource is invalid f.ex in

    an initializeObject override in the SDO.

    We have fixed the SDO to work with ForeignFields without a DataSource, so

    the filter should be fixed accordingly, so this will be fixed if an issue is

    entered or a bug is reported.

    Havard

    -Original Message-

    From: Wim van der Ham

    Sent: Wednesday, December 11, 2002 5:57 AM

    To: dev@adm2.possenet.org

    Subject: Filter problem with parent - child SDO relation

    Hello all,

    I have a problem with the dynamic filter in the ADM2.

    I've not yet circumcised the problem completely but it happens when I want

    to filter on a field in a SDO which is also the foreign field for another

    SDO.

    Example:

    - SmartWindow

    - SDO Parent

    - SDO Child (linked to parent through a foreign field)

    - Dynfilter

    - Browse Parent (showing records from parent sdo)

    - Browse Child (showing records from child sdo)

    Links are (besides the obvious container links and data links between sdo

    and browse):

    SDO Parent data SDO Child (with foreign field)

    Dynfilter - filter SDO Parent (filter on field which is also the

    foreign field for the data link between the two SDO's)

    When I try to create this situation the following happens:

    - The filter field is shown as READ-ONLY so it's impossible to filter on

    - No operator is shown besides the filter field

    - An error message comes up (Entry 2 is out of range) when the window is

    first started. Debugging the adm2 filter.p super procedure shows that this

    error comes in the dataAvailable procedure at the point where foreignvalues

    are processed. Although the SDO has foreign fields, there are no foreign

    values because it's the PARENT of the relation between SDO's.

    It seems that the dynfilter doesn't take into account the fact that the SDO

    that he's filtering on is the PARENT of a foreign field relation, rather

    then the CHILD. I understand that it shouldn't be allowed to filter on a

    foreign field if that field is already supplied by a parent SDO, but in

    this case the SDO on which the filter operates is the PARENT.

    I'm on V9.1C20.

    Can someone explain how to solve this bug?

    Best regards,

    Wim

    _________________________________________________

    Ing. Wilhelmus van der Ham

    WITS - Worldwide IT Solutions sas

    di Wilhelmus van der Ham & C.

    Italian partner for DWP: http://www.dynamicwebclient.info

    via Motrassino, 2

    10078 Venaria-Reale (TO) - Italy

    Internet: http://www.wits.it

    Telephone: +39-011-4527691

    Mobile Phone: +39-335-6877283

    Mobile Fax: +39-335-0-6877283

    To unsubscribe, e-mail: dev-unsubscribe@adm2.possenet.org

    For additional commands, e-mail: dev-help@adm2.possenet.org

    To unsubscribe, e-mail: dev-unsubscribe@adm2.possenet.org

    For additional commands, e-mail: dev-help@adm2.possenet.org

  • I've found the problem!

    The parent SDO STILL had the foreign fields specified because initially the

    link was the other way around...

    When the link direction was changed, the foreign fields property wasn't

    blanked out, thus leaving BOTH SDO's with foreign fields where only the

    CHILD should have the property.

    Deleting the instance and re-adding solved the problem.

    I don't know if we can consider a bug the fact that a SDO without parent

    has foreign fields. Especially when you say that the link could be added

    from somewhere outside of the window.

    Thanks for your help,

    Wim

    At 19:34 11/12/2002 -0500, Havard Danielsen wrote:

    The ForeignFields property is only used by SDOs that have a parent, so maybe

    you can set it to blank?

    If the ForeignFields is defined because this Window also can be called from

    another Window that adds another SDO as a parent with pass-thru link, then

    you may need to do this conditionally when the DataSource is invalid f.ex in

    an initializeObject override in the SDO.

    We have fixed the SDO to work with ForeignFields without a DataSource, so

    the filter should be fixed accordingly, so this will be fixed if an issue is

    entered or a bug is reported.

    Havard

    -Original Message-

    From: Wim van der Ham

    Sent: Wednesday, December 11, 2002 5:57 AM

    To: dev@adm2.possenet.org

    Subject: Filter problem with parent - child SDO relation

    Hello all,

    I have a problem with the dynamic filter in the ADM2.

    I've not yet circumcised the problem completely but it happens when I want

    to filter on a field in a SDO which is also the foreign field for another

    SDO.

    Example:

    - SmartWindow

    - SDO Parent

    - SDO Child (linked to parent through a foreign field)

    - Dynfilter

    - Browse Parent (showing records from parent sdo)

    - Browse Child (showing records from child sdo)

    Links are (besides the obvious container links and data links between sdo

    and browse):

    SDO Parent data SDO Child (with foreign field)

    Dynfilter - filter SDO Parent (filter on field which is also the

    foreign field for the data link between the two SDO's)

    When I try to create this situation the following happens:

    - The filter field is shown as READ-ONLY so it's impossible to filter on

    - No operator is shown besides the filter field

    - An error message comes up (Entry 2 is out of range) when the window is

    first started. Debugging the adm2 filter.p super procedure shows that this

    error comes in the dataAvailable procedure at the point where foreignvalues

    are processed. Although the SDO has foreign fields, there are no foreign

    values because it's the PARENT of the relation between SDO's.

    It seems that the dynfilter doesn't take into account the fact that the SDO

    that he's filtering on is the PARENT of a foreign field relation, rather

    then the CHILD. I understand that it shouldn't be allowed to filter on a

    foreign field if that field is already supplied by a parent SDO, but in

    this case the SDO on which the filter operates is the PARENT.

    I'm on V9.1C20.

    Can someone explain how to solve this bug?

    Best regards,

    Wim

    _________________________________________________

    Ing. Wilhelmus van der Ham

    WITS - Worldwide IT Solutions sas

    di Wilhelmus van der Ham & C.

    Italian partner for DWP: http://www.dynamicwebclient.info

    via Motrassino, 2

    10078 Venaria-Reale (TO) - Italy

    Internet: http://www.wits.it

    Telephone: +39-011-4527691

    Mobile Phone: +39-335-6877283

    Mobile Fax: +39-335-0-6877283

    To unsubscribe, e-mail: dev-unsubscribe@adm2.possenet.org

    For additional commands, e-mail: dev-help@adm2.possenet.org

    To unsubscribe, e-mail: dev-unsubscribe@adm2.possenet.org

    For additional commands, e-mail: dev-help@adm2.possenet.org

    _________________________________________________

    Ing. Wilhelmus van der Ham

    WITS - Worldwide IT Solutions sas

    di Wilhelmus van der Ham & C.

    Italian partner for DWP: http://www.dynamicwebclient.info

    via Motrassino, 2

    10078 Venaria-Reale (TO) - Italy

    Internet: http://www.wits.it

    Telephone: +39-011-4527691

    Mobile Phone: +39-335-6877283

    Mobile Fax: +39-335-0-6877283

    To unsubscribe, e-mail: dev-unsubscribe@adm2.possenet.org

    For additional commands, e-mail: dev-help@adm2.possenet.org

  • Hello all,

    Looking for help in the old mail, I met with this one.

    What I am attempting, without any success, is the following :

    Having alone a SDO and a SDB in a Smart-Widow.

    I want to use ForeignFields to filter the SDO.

    Havard says... "We have fixed the SDO to work with ForeignFields without to DataSource"

    I says... I want it!! in that version of Progress / ADM ??

    How I have to use ???

    Now i do : setForeignFields..., setForeignValues... , and OpenQuey..., but it doesn't happen anything.

    TIA ..

    JAO

    From a hot Argentina.. more hot than a Dolar * 10 !! .

    -Mensaje original-

    De: Havard Danielsen

    Enviado el: Miércoles, 11 de Diciembre de 2002 09:35 p.m.

    Para: dev@adm2.possenet.org

    Asunto: RE: Filter problem with parent - child SDO relation

    The ForeignFields property is only used by SDOs that have a parent, so maybe

    you can set it to blank?

    If the ForeignFields is defined because this Window also can be called from

    another Window that adds another SDO as a parent with pass-thru link, then

    you may need to do this conditionally when the DataSource is invalid f.ex in

    an initializeObject override in the SDO.

    We have fixed the SDO to work with ForeignFields without a DataSource, so

    the filter should be fixed accordingly, so this will be fixed if an issue is

    entered or a bug is reported.

    Havard

    -Original Message-

    From: Wim van der Ham

    Sent: Wednesday, December 11, 2002 5:57 AM

    To: dev@adm2.possenet.org

    Subject: Filter problem with parent - child SDO relation

    Hello all,

    I have a problem with the dynamic filter in the ADM2.

    I've not yet circumcised the problem completely but it happens when I want

    to filter on a field in a SDO which is also the foreign field for another

    SDO.

    Example:

    - SmartWindow

    - SDO Parent

    - SDO Child (linked to parent through a foreign field)

    - Dynfilter

    - Browse Parent (showing records from parent sdo)

    - Browse Child (showing records from child sdo)

    Links are (besides the obvious container links and data links between sdo

    and browse):

    SDO Parent data SDO Child (with foreign field)

    Dynfilter - filter SDO Parent (filter on field which is also the

    foreign field for the data link between the two SDO's)

    When I try to create this situation the following happens:

    - The filter field is shown as READ-ONLY so it's impossible to filter on

    - No operator is shown besides the filter field

    - An error message comes up (Entry 2 is out of range) when the window is

    first started. Debugging the adm2 filter.p super procedure shows that this

    error comes in the dataAvailable procedure at the point where foreignvalues

    are processed. Although the SDO has foreign fields, there are no foreign

    values because it's the PARENT of the relation between SDO's.

    It seems that the dynfilter doesn't take into account the fact that the SDO

    that he's filtering on is the PARENT of a foreign field relation, rather

    then the CHILD. I understand that it shouldn't be allowed to filter on a

    foreign field if that field is already supplied by a parent SDO, but in

    this case the SDO on which the filter operates is the PARENT.

    I'm on V9.1C20.

    Can someone explain how to solve this bug?

    Best regards,

    Wim

    _________________________________________________

    Ing. Wilhelmus van der Ham

    WITS - Worldwide IT Solutions sas

    di Wilhelmus van der Ham & C.

    Italian partner for DWP: http://www.dynamicwebclient.info

    via Motrassino, 2

    10078 Venaria-Reale (TO) - Italy

    Internet: http://www.wits.it

    Telephone: +39-011-4527691

    Mobile Phone: +39-335-6877283

    Mobile Fax: +39-335-0-6877283

    To unsubscribe, e-mail: dev-unsubscribe@adm2.possenet.org

    For additional commands, e-mail: dev-help@adm2.possenet.org

    To unsubscribe, e-mail: dev-unsubscribe@adm2.possenet.org

    For additional commands, e-mail: dev-help@adm2.possenet.org

    To unsubscribe, e-mail: dev-unsubscribe@adm2.possenet.org

    For additional commands, e-mail: dev-help@adm2.possenet.org

  • I'm afraid that this fix is the opposite of what you want as it will ignore

    the foreignFields when there is no datasource.

    If you want to add a fixed part of the query that cannot be changed by

    filters later then try to add this with addQueryWhere.

    On newer version you may also setBaseQuery, but this has to be done very

    early.

    HÃ¥vard

    -Original Message-

    From: OYHANART JUAN

    Sent: Friday, January 31, 2003 10:53 AM

    To: dev@adm2.possenet.org

    Cc: hdaniels@progress.com

    Subject: RE: Filter problem with parent - child SDO relation

    Hello all,

    Looking for help in the old mail, I met with this one.

    What I am attempting, without any success, is the following :

    Having alone a SDO and a SDB in a Smart-Widow.

    I want to use ForeignFields to filter the SDO.

    Havard says... "We have fixed the SDO to work with ForeignFields without

    to DataSource"

    I says... I want it!! in that version of Progress / ADM ??

    How I have to use ???

    Now i do : setForeignFields..., setForeignValues... , and OpenQuey..., but

    it doesn't happen anything.

    TIA ..

    JAO

    From a hot Argentina.. more hot than a Dolar * 10 !! .

    -Mensaje original-

    De: Havard Danielsen

    Enviado el: Miércoles, 11 de Diciembre de 2002 09:35 p.m.

    Para: dev@adm2.possenet.org

    Asunto: RE: Filter problem with parent - child SDO relation

    The ForeignFields property is only used by SDOs that have a parent, so maybe

    you can set it to blank?

    If the ForeignFields is defined because this Window also can be called from

    another Window that adds another SDO as a parent with pass-thru link, then

    you may need to do this conditionally when the DataSource is invalid f.ex in

    an initializeObject override in the SDO.

    We have fixed the SDO to work with ForeignFields without a DataSource, so

    the filter should be fixed accordingly, so this will be fixed if an issue is

    entered or a bug is reported.

    Havard

    -Original Message-

    From: Wim van der Ham

    Sent: Wednesday, December 11, 2002 5:57 AM

    To: dev@adm2.possenet.org

    Subject: Filter problem with parent - child SDO relation

    Hello all,

    I have a problem with the dynamic filter in the ADM2.

    I've not yet circumcised the problem completely but it happens when I want

    to filter on a field in a SDO which is also the foreign field for another

    SDO.

    Example:

    - SmartWindow

    - SDO Parent

    - SDO Child (linked to parent through a foreign field)

    - Dynfilter

    - Browse Parent (showing records from parent sdo)

    - Browse Child (showing records from child sdo)

    Links are (besides the obvious container links and data links between sdo

    and browse):

    SDO Parent data SDO Child (with foreign field)

    Dynfilter - filter SDO Parent (filter on field which is also the

    foreign field for the data link between the two SDO's)

    When I try to create this situation the following happens:

    - The filter field is shown as READ-ONLY so it's impossible to filter on

    - No operator is shown besides the filter field

    - An error message comes up (Entry 2 is out of range) when the window is

    first started. Debugging the adm2 filter.p super procedure shows that this

    error comes in the dataAvailable procedure at the point where foreignvalues

    are processed. Although the SDO has foreign fields, there are no foreign

    values because it's the PARENT of the relation between SDO's.

    It seems that the dynfilter doesn't take into account the fact that the SDO

    that he's filtering on is the PARENT of a foreign field relation, rather

    then the CHILD. I understand that it shouldn't be allowed to filter on a

    foreign field if that field is already supplied by a parent SDO, but in

    this case the SDO on which the filter operates is the PARENT.

    I'm on V9.1C20.

    Can someone explain how to solve this bug?

    Best regards,

    Wim

    _________________________________________________

    Ing. Wilhelmus van der Ham

    WITS - Worldwide IT Solutions sas

    di Wilhelmus van der Ham & C.

    Italian partner for DWP: http://www.dynamicwebclient.info

    via Motrassino, 2

    10078 Venaria-Reale (TO) - Italy

    Internet: http://www.wits.it

    Telephone: +39-011-4527691

    Mobile Phone: +39-335-6877283

    Mobile Fax: +39-335-0-6877283

    To unsubscribe, e-mail: dev-unsubscribe@adm2.possenet.org

    For additional commands, e-mail: dev-help@adm2.possenet.org

    To unsubscribe, e-mail: dev-unsubscribe@adm2.possenet.org

    For additional commands, e-mail: dev-help@adm2.possenet.org

    To unsubscribe, e-mail: dev-unsubscribe@adm2.possenet.org

    For additional commands, e-mail: dev-help@adm2.possenet.org

  • Thank´s for you help.

    1.- I understand that I don't need the fix . Would make the worst things.

    2.- I use the addQueryWhere for the user filter.

    3.- I think this is what i need ... "setBaseQuery".

    This is my situation

    I have the initial query of the SDO.

    I have the filters characteristic of the window. (I try to use setForeignFields )

    I have the filters characteristic of the user. ( addQueryWhere )

    The problem ... The OpenQquery ignore the "setForeignFields" if I set manually.

    Is there something that I can make??

    It is complicated to download from posse, alone the setBaseQuery part? Is it isolated ?

    Environment :

    Version 9.1D

    POSSE Version 2.0

    Thak´s again and excuse the poor English

    JAO From Argentina even more hot and cheap!

    -Mensaje original-

    De: Havard Danielsen

    Enviado el: Viernes, 31 de Enero de 2003 01:00 p.m.

    Para: OYHANART JUAN; dev@adm2.possenet.org

    Asunto: RE: Filter problem with parent - child SDO relation

    I'm afraid that this fix is the opposite of what you want as it will ignore

    the foreignFields when there is no datasource.

    If you want to add a fixed part of the query that cannot be changed by

    filters later then try to add this with addQueryWhere.

    On newer version you may also setBaseQuery, but this has to be done very

    early.

    HÃ¥vard

    -Original Message-

    From: OYHANART JUAN

    Sent: Friday, January 31, 2003 10:53 AM

    To: dev@adm2.possenet.org

    Cc: hdaniels@progress.com

    Subject: RE: Filter problem with parent - child SDO relation

    Hello all,

    Looking for help in the old mail, I met with this one.

    What I am attempting, without any success, is the following :

    Having alone a SDO and a SDB in a Smart-Widow.

    I want to use ForeignFields to filter the SDO.

    Havard says... "We have fixed the SDO to work with ForeignFields without

    to DataSource"

    I says... I want it!! in that version of Progress / ADM ??

    How I have to use ???

    Now i do : setForeignFields..., setForeignValues... , and OpenQuey..., but

    it doesn't happen anything.

    TIA ..

    JAO

    From a hot Argentina.. more hot than a Dolar * 10 !! .

    -Mensaje original-

    De: Havard Danielsen

    Enviado el: Miércoles, 11 de Diciembre de 2002 09:35 p.m.

    Para: dev@adm2.possenet.org

    Asunto: RE: Filter problem with parent - child SDO relation

    The ForeignFields property is only used by SDOs that have a parent, so maybe

    you can set it to blank?

    If the ForeignFields is defined because this Window also can be called from

    another Window that adds another SDO as a parent with pass-thru link, then

    you may need to do this conditionally when the DataSource is invalid f.ex in

    an initializeObject override in the SDO.

    We have fixed the SDO to work with ForeignFields without a DataSource, so

    the filter should be fixed accordingly, so this will be fixed if an issue is

    entered or a bug is reported.

    Havard

    -Original Message-

    From: Wim van der Ham

    Sent: Wednesday, December 11, 2002 5:57 AM

    To: dev@adm2.possenet.org

    Subject: Filter problem with parent - child SDO relation

    Hello all,

    I have a problem with the dynamic filter in the ADM2.

    I've not yet circumcised the problem completely but it happens when I want

    to filter on a field in a SDO which is also the foreign field for another

    SDO.

    Example:

    - SmartWindow

    - SDO Parent

    - SDO Child (linked to parent through a foreign field)

    - Dynfilter

    - Browse Parent (showing records from parent sdo)

    - Browse Child (showing records from child sdo)

    Links are (besides the obvious container links and data links between sdo

    and browse):

    SDO Parent data SDO Child (with foreign field)

    Dynfilter - filter SDO Parent (filter on field which is also the

    foreign field for the data link between the two SDO's)

    When I try to create this situation the following happens:

    - The filter field is shown as READ-ONLY so it's impossible to filter on

    - No operator is shown besides the filter field

    - An error message comes up (Entry 2 is out of range) when the window is

    first started. Debugging the adm2 filter.p super procedure shows that this

    error comes in the dataAvailable procedure at the point where foreignvalues

    are processed. Although the SDO has foreign fields, there are no foreign

    values because it's the PARENT of the relation between SDO's.

    It seems that the dynfilter doesn't take into account the fact that the SDO

    that he's filtering on is the PARENT of a foreign field relation, rather

    then the CHILD. I understand that it shouldn't be allowed to filter on a

    foreign field if that field is already supplied by a parent SDO, but in

    this case the SDO on which the filter operates is the PARENT.

    I'm on V9.1C20.

    Can someone explain how to solve this bug?

    Best regards,

    Wim

    _________________________________________________

    Ing. Wilhelmus van der Ham

    WITS - Worldwide IT Solutions sas

    di Wilhelmus van der Ham & C.

    Italian partner for DWP: http://www.dynamicwebclient.info

    via Motrassino, 2

    10078 Venaria-Reale (TO) - Italy

    Internet: http://www.wits.it

    Telephone: +39-011-4527691

    Mobile Phone: +39-335-6877283

    Mobile Fax: +39-335-0-6877283

    To unsubscribe, e-mail: dev-unsubscribe@adm2.possenet.org

    For additional commands, e-mail: dev-help@adm2.possenet.org

    To unsubscribe, e-mail: dev-unsubscribe@adm2.possenet.org

    For additional commands, e-mail: dev-help@adm2.possenet.org

    To unsubscribe, e-mail: dev-unsubscribe@adm2.possenet.org

    For additional commands, e-mail: dev-help@adm2.possenet.org

  • I do not understand completely.

    I do not think you will have any success with ForeignFields if you do not

    have a datasource.

    If you use assignQuerySelection for user filters then you can use

    removeQuerySelection to remove them and the criteria added with

    addQueryWhere will stay intact.

    BaseQuery is not isolated... You could, however, try to setOpenQuery (or

    QueryOpen?), which is very similar. (It may go directly to the AppServer)

    HÃ¥vard

    -Original Message-

    From: OYHANART JUAN

    Sent: Friday, January 31, 2003 11:31 AM

    To: Havard Danielsen

    Cc: dev@adm2.possenet.org

    Subject: RE: Filter problem with parent - child SDO relation

    Thank´s for you help.

    1.- I understand that I don't need the fix . Would make the worst things.

    2.- I use the addQueryWhere for the user filter.

    3.- I think this is what i need ... "setBaseQuery".

    This is my situation

    I have the initial query of the SDO.

    I have the filters characteristic of the window. (I try to use

    setForeignFields )

    I have the filters characteristic of the user. ( addQueryWhere )

    The problem ... The OpenQquery ignore the "setForeignFields" if I set

    manually.

    Is there something that I can make??

    It is complicated to download from posse, alone the setBaseQuery part? Is it

    isolated ?

    Environment :

    Version 9.1D

    POSSE Version 2.0

    Thak´s again and excuse the poor English

    JAO From Argentina even more hot and cheap!

    -Mensaje original-

    De: Havard Danielsen

    Enviado el: Viernes, 31 de Enero de 2003 01:00 p.m.

    Para: OYHANART JUAN; dev@adm2.possenet.org

    Asunto: RE: Filter problem with parent - child SDO relation

    I'm afraid that this fix is the opposite of what you want as it will ignore

    the foreignFields when there is no datasource.

    If you want to add a fixed part of the query that cannot be changed by

    filters later then try to add this with addQueryWhere.

    On newer version you may also setBaseQuery, but this has to be done very

    early.

    HÃ¥vard

    -Original Message-

    From: OYHANART JUAN

    Sent: Friday, January 31, 2003 10:53 AM

    To: dev@adm2.possenet.org

    Cc: hdaniels@progress.com

    Subject: RE: Filter problem with parent - child SDO relation

    Hello all,

    Looking for help in the old mail, I met with this one.

    What I am attempting, without any success, is the following :

    Having alone a SDO and a SDB in a Smart-Widow.

    I want to use ForeignFields to filter the SDO.

    Havard says... "We have fixed the SDO to work with ForeignFields without

    to DataSource"

    I says... I want it!! in that version of Progress / ADM ??

    How I have to use ???

    Now i do : setForeignFields..., setForeignValues... , and OpenQuey..., but

    it doesn't happen anything.

    TIA ..

    JAO

    From a hot Argentina.. more hot than a Dolar * 10 !! .

    -Mensaje original-

    De: Havard Danielsen

    Enviado el: Miércoles, 11 de Diciembre de 2002 09:35 p.m.

    Para: dev@adm2.possenet.org

    Asunto: RE: Filter problem with parent - child SDO relation

    The ForeignFields property is only used by SDOs that have a parent, so maybe

    you can set it to blank?

    If the ForeignFields is defined because this Window also can be called from

    another Window that adds another SDO as a parent with pass-thru link, then

    you may need to do this conditionally when the DataSource is invalid f.ex in

    an initializeObject override in the SDO.

    We have fixed the SDO to work with ForeignFields without a DataSource, so

    the filter should be fixed accordingly, so this will be fixed if an issue is

    entered or a bug is reported.

    Havard

    -Original Message-

    From: Wim van der Ham

    Sent: Wednesday, December 11, 2002 5:57 AM

    To: dev@adm2.possenet.org

    Subject: Filter problem with parent - child SDO relation

    Hello all,

    I have a problem with the dynamic filter in the ADM2.

    I've not yet circumcised the problem completely but it happens when I want

    to filter on a field in a SDO which is also the foreign field for another

    SDO.

    Example:

    - SmartWindow

    - SDO Parent

    - SDO Child (linked to parent through a foreign field)

    - Dynfilter

    - Browse Parent (showing records from parent sdo)

    - Browse Child (showing records from child sdo)

    Links are (besides the obvious container links and data links between sdo

    and browse):

    SDO Parent data SDO Child (with foreign field)

    Dynfilter - filter SDO Parent (filter on field which is also the

    foreign field for the data link between the two SDO's)

    When I try to create this situation the following happens:

    - The filter field is shown as READ-ONLY so it's impossible to filter on

    - No operator is shown besides the filter field

    - An error message comes up (Entry 2 is out of range) when the window is

    first started. Debugging the adm2 filter.p super procedure shows that this

    error comes in the dataAvailable procedure at the point where foreignvalues

    are processed. Although the SDO has foreign fields, there are no foreign

    values because it's the PARENT of the relation between SDO's.

    It seems that the dynfilter doesn't take into account the fact that the SDO

    that he's filtering on is the PARENT of a foreign field relation, rather

    then the CHILD. I understand that it shouldn't be allowed to filter on a

    foreign field if that field is already supplied by a parent SDO, but in

    this case the SDO on which the filter operates is the PARENT.

    I'm on V9.1C20.

    Can someone explain how to solve this bug?

    Best regards,

    Wim

    _________________________________________________

    Ing. Wilhelmus van der Ham

    WITS - Worldwide IT Solutions sas

    di Wilhelmus van der Ham & C.

    Italian partner for DWP: http://www.dynamicwebclient.info

    via Motrassino, 2

    10078 Venaria-Reale (TO) - Italy

    Internet: http://www.wits.it

    Telephone: +39-011-4527691

    Mobile Phone: +39-335-6877283

    Mobile Fax: +39-335-0-6877283

    To unsubscribe, e-mail: dev-unsubscribe@adm2.possenet.org

    For additional commands, e-mail: dev-help@adm2.possenet.org

    To unsubscribe, e-mail: dev-unsubscribe@adm2.possenet.org

    For additional commands, e-mail: dev-help@adm2.possenet.org

    To unsubscribe, e-mail: dev-unsubscribe@adm2.possenet.org

    For additional commands, e-mail: dev-help@adm2.possenet.org