10.2.1 Form designer Join criteria (OpenInsight 64-bit)
At 16 MAY 2024 06:27:07AM Nick Stevenson wrote:
Forms all migrated from OI9.4.4.
Form has multiple tables, migration correctly set up the Join criteria, all works fine.
Add a new databound control to the form in 10.2.1, the Join criteria mysteriously disappears without notice and the form hangs when run.
Have to then add the Join criteria back on.
At 28 MAY 2024 04:24AM Carl Pates wrote:
Hi Nick,
What sort of join criteria are we talking about here? One to one? One to many (editTable etc …) Single key, multipart key? If you can give me an example I'll try and reproduce and get the problem fixed.
Does the join criteria stay if you add another control or does it disappear again (i.e. does it stay fixed?)
Thanks,
At 28 MAY 2024 06:50AM Nick Stevenson wrote:
Hi Carl
One to many - typically an edit table using a relational index off the primary table to display many rows in a joined table (eg: CUSTOMER → CUSTOMER_ORDERS). Always single part keys.
This error may only apply to forms straight out the migration box - ie if they have been fixed then the error no longer occurs.
I say this because I can no longer replicate the error on the form that caused the problem, it was fixed (the join criteria re-added).
However, I have noticed the following and it could be cause for concern.
In OI9, the join criteria would always show the form edit table control name, the edit table column header text (incl spaces) and the edit table column number, delimited with dot eg: "CONTRACT_TABLE.Control ID.1"
In OI10, when adding a new join criteria, the Edit Form Table Join Criteria dialog box will initially show the exact edit table column selected (as per OI9) - "CONTRACT_TABLE.Control ID.1", but if you save the Edit Form Table Join Criteria dialog box and then immediately re-open it, you'd see "CONTRACT_TABLE." (ie, just the edit table name and a trailing dot - the rest has disappeared.
Then if you save the form, close and re-open it, you would see just "CONTRACT_TABLE" - ie the trailing dot has now disappeared. This caused a problem when the joined table key field was not in column 1.
I hope this helps!
Nick
At 29 MAY 2024 11:52AM Carl Pates wrote:
Hi Nick,
Should be fixed for v10.2.2
Regards