08-08-2019, 06:34 AM
I have included 3 images to show the result and hope a visualization helps.
First image show the full content of the table. (SQL call without Where clause)
Second image show only those rows with an S in them (note the S in the IWEdit above) after a new SQL call with Where LokationNavn like '%s%'
Third image show the lot less rows with SV in them. (SQL call with where LokationNavn like '%sv%')
Changes are done in the Keypress method of IWEdit1 and the grid is shown with all SQL rows satisfying the selection. For each SQL call, I do reset Grid TOP, HEIGHT and ROWCOUNT to designed values, as well as do a IWGrid1.clear to empty all cells.
And there are two issues:
Why do the Grid change the height of the cells, when there are less rows than what would fill the size of the grid, if rows had normal height ?
Why do the Grid change it's position ? The value of top is still the same but obviously and visually it has moved.
First image show the full content of the table. (SQL call without Where clause)
Second image show only those rows with an S in them (note the S in the IWEdit above) after a new SQL call with Where LokationNavn like '%s%'
Third image show the lot less rows with SV in them. (SQL call with where LokationNavn like '%sv%')
Changes are done in the Keypress method of IWEdit1 and the grid is shown with all SQL rows satisfying the selection. For each SQL call, I do reset Grid TOP, HEIGHT and ROWCOUNT to designed values, as well as do a IWGrid1.clear to empty all cells.
And there are two issues:
Why do the Grid change the height of the cells, when there are less rows than what would fill the size of the grid, if rows had normal height ?
Why do the Grid change it's position ? The value of top is still the same but obviously and visually it has moved.