DBAdvGrid Error while adding new record and when editing an existing record

[Francisco_Alvarado]

Hi:
Since the last few versions I have this error when adding a record and using tab to go to next record:

EditPostMode is epRow, PageMode is True and I tired different setting for all relative properties.
(MS SQL Server ver 15 and ver 17, W10 and W11)
The field UserName is not a key field and can accept nulls:

When editing, the table goes to dsBrowse status preventing to keep editing next fields. I reported this issue some time ago...
Searching the forum I found an old post reporting the same problem:

EditPostMode := epCell in TDBAdvGrid.ActiveChange

The following lines of Code have been added somewhere between Version 2.3.8.6 and 2.4.4.7 of DBAdvGrid.pas to TDBAdvGrid.ActiveChange: if not (csDesigning in ComponentState) then begin if Navigation.AppendOnArrowDown then EditPostMode := epCell; end; What is the intended purpose of this addition? It causes quite some problems for our product. I don't think it is correct to overwrite public properties like EditPostMode during run-time without Input from the developer. With a public prop…

I looked the lines mentioned in it and in the last version of DBAdvGrid (2.8.3.5) are commented.
Now this is a big issue for me as all my applications use this interface.
Are you aware of this issue and did you find a solution? I'm importing all records from xlsx files to avoid this problem...
Best Regards
Francisco Alvarado

1. List item

[brunofierens]

I'm not seeing how this change could be relevant as this it is applicable for EditPostMode epCell and you indicate you use epRow?
Can this be reproduced with any of the demos (or a modified demo)?

[Francisco_Alvarado]

Hi Bruno
Since I reported the edit issue I tried to modify some demos, but I think it's related to the dataset, as you responded at that time...

@brunofierens

There is an incompatibility with the dataset handling when EditPostMode = epRow when Navigation.AppendOnArrowDown is used. Therefore, to avoid this possible conflict, we forced it this way.

I don't use Navigation.AppendOnArrowDown since all the append and edit of records is done in a panel, but maybe the problem is still related to a dataset incompatibility...
I'll prepare a demo using MS-SQL Server tables to reproduce the problem.
Best Regards
Francisco Alvarado

[brunofierens]

Preferably if you can with a TClientDataSet for easy deployment so we have a setup to test as standalone as possible.