2 replies to this topic

[rond]

If you add a TNxVirtualcolumn to a NextDbGrid then you will get access violations whenever you forget to check if the column you want to use is an actual TNxDbColumn as the TNxVirtualColumn don't have the same ancestral-class ...

The column-designer for the grid also allows you to add this TNxVirtualColumn even though it is incompatible with this grid.

[Boki (Berg)]

Hello Rond,

Please sorry for delay.

I have test it now and all seems to be fine. Do I need to do something more? Thank you.

Best regards

[rond]

All I did was call BestFitColumn(i, bfBoth) for all the columns, except the ones that had 'autosize' set.
As there were a few virtualcolumns I got an exception for both of them, until I excluded them with code like this :

CODE

for i := 0 to aGrid.Columns.Count - 1 do
begin
try
if not (TNxCustomColumn(aGrid.Columns[i]) is TNxVirtualColumn) then
begin
if not (coAutoSize in aGrid.Columns[i].Options) and (not (TNxCustomColumn(aGrid.Columns[i]) is TNxVirtualColumn)) then
aGrid.BestFitColumn(i, bfBoth);
end;
except
on e : exception do
begin
end;
end;
end;