Page 4 of 4

Re: Strange behavior of the Select field

Posted: Fri Apr 26, 2024 5:43 pm
by kknm
All subforms are unrelated to each other - there is only one common field with the date. All other forms work correctly, only the co_put table has problems. Is it possible to ignore the other forms?

I uploaded cogp.sql to another database.
Based on the loaded table cogp_tab, I created the form tab_cogp. Changed the fio field property - - no check for empty value.

I didn't touch the other forms. The problem form c_p behaves similarly to the problem described earlier, i.e. its behavior does not depend on other forms!!!!
It took 5 minutes...

Re: Strange behavior of the Select field

Posted: Sat Apr 27, 2024 4:18 pm
by kev1n
I changed the SQL of cogp_p from

Code: Select all

SELECT
 co_put.*,
    cogp_tab.*

FROM
    co_put
        JOIN cogp_tab ON co_put.p_tab = cogp_tab.tab_id

to

Code: Select all

SELECT * FROM `co_put`
and saving seems to work now.

Re: Strange behavior of the Select field

Posted: Sat Apr 27, 2024 7:37 pm
by kknm
Kevin, thanks for spending your time on the weekend, but the line

JOIN cogp_tab ON co_put.p_tab = cogp_tab.tab_id

means that the co_put table receives the date from another table - cogp_tab. Also, 4 other subforms on this form receive the same date in the same way, and they work correctly.
There must be another reason for this behavior

Re: Strange behavior of the Select field

Posted: Sat Apr 27, 2024 8:55 pm
by kknm
gd.png
svod.png
pro.png
pers.png
put.png

Re: Strange behavior of the Select field

Posted: Sat Apr 27, 2024 11:56 pm
by kknm
Kevin, you won't believe this, but the problem was in the SELECT field.

I took the code from the help and assigned a list like this:
0|Loaded|1|Empty

After several days of torment, I simply brought the list to this form:
1|Loaded|2|Empty

You can’t imagine what my surprise was - everything worked correctly right away!!!
Of course, I will continue to watch, because I can’t believe such a glitch.
Thank you for participating !!!