> There is a horrible bug in ORDA where regardless of which field the relation
> is
> drawn to in the one table, it will always locate the one record by querying on
> the primary key field of the one record using the value you have entered into
> the many field.
Justin,
I just ran a couple of tests of this issue in a new structure (4D v17r5,
Windows 10). I cannot reproduce the results you are seeing
Test 1:
Table_1 -> Table_2 not using primary keys at all
ORDA query Table_1 on other key follow relation to Table_2 (again that
doesn't go to primarykey)
Success
Test 2:
Table_1 -> Table_2 not using primary keys at all
ORDA query Table_2 on other key follow relation to Table_1 (again that
doesn't go to primarykey)
Success
Neil
Privacy Disclaimer: This message contains confidential information and is
intended only for the named addressee. If you are not the named addressee you
should not disseminate, distribute or copy this email. Please delete this email
from your system and notify the sender immediately by replying to this email.
If you are not the intended recipient you are notified that disclosing,
copying, distributing or taking any action in reliance on the contents of this
information is strictly prohibited.
The Alternative Investments division of UMB Fund Services provides a full range
of services to hedge funds, funds of funds and private equity funds. Any tax
advice in this communication is not intended to be used, and cannot be used, by
a client or any other person or entity for the purpose of (a) avoiding
penalties that may be imposed on any taxpayer or (b) promoting, marketing, or
recommending to another party any matter addressed herein.
**********************************************************************
4D Internet Users Group (4D iNUG)
Archive: http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:[email protected]
**********************************************************************
