IndexedDB on Secondary Form

WEB TMS WEB Core
1

Hi,

I am having some really strange issues, such as record not being located when clicking on a TWebDBResponsiveGrid item, using IndexedDB on any form other than the main form. Doing the same thing on the MainForm works fine. The IndexedDB is filtered.

Is there anything I should be aware of when doing this?

Thanks,

Ken

2

Do you have more details?
Is this using the same connection on both main screen & detail screen? same table(s)? Is the 2nd screen a popup form or new opened form? Other relevant details?

3

It is using a different connections but is the same underlying table. The 2nd form is not a popup but it is modal.

4

Can you isolate this and send a sample source project with which we can reproduce this & investigate?

5

I will attempt to do so.

6

I have more info for you. The 2nd form was a red herring I'm afraid and the problem exists in all cases. This is only when two indexed db tables are used and selecting one filters the otherin the after scroll event.. The 2nd table has to be closed and reopened otherwise the filter does not happen.

When selecting an item in the first TWebDBResponsiveGrid it displays everything correctly in the 2nd TWebDBResponsiveGrid. Clicking on an item in the 2nd TWebDBResponsiveGrid automatically selects the correct record in the 2nd table ONLY if it is the first record in the ist table.

Does this make sense?

7

Example attached: Two IndexedDB Tables.zip (8.8 KB)

I don't think I am doing anything wrong as both grids display correctly.

Three problems:

  1. If I don't use the Sleep function after database activity, even though await is being used it crashes.
  2. Even though in the onscroll event I set the ItemIndex to zero the corresponding item is not selected in the child grid other than for the top item in the main grid.
  3. Selecting the child item and clicking on the Show Record Info button displays the wrong field name. Again, it works for the top item in the main grid.

I'm rather stumped by this.

Thanks,

Ken

8

I should add that I am using Firefox but have tested on Chrome and Edge with same results.

9

We traced & solved this issue that was in TWebDBResponsiveGrid. The next update will address this.

10

Thanks Bruno, any idea when it will be available as I cannot continue with my project without this fix?

11

We aim for this month.

12

Is it possible to get the changes?

13

There is a lot of code in flux right now in preparation for v2.0, so sending the involved updated files can potentially break with v1.9.