When adding a new row & only entering a value in the sort column of a GDBG before moving to another new row, the corresponding column in an existing row can be corrupted.
I have created an example which displays 2 columns from the Northwind.Customers table. If you start adding a new row by typing Wo in the first col & then hit the down arrow key to add another record (without entering anything in col2), you will see the effect.
If you repeat the process but tab into col2 before adding the row, there is no problem.
I first encountered the problem in a table which only displayed 1 column.
Any ideas on how to get round this?