>
>You're not violating a .dbc trigger, are you?
>

No rules, no triggers.

It gets better.

Unless I movethe record pointer in the grid, then the records don't appear in the right place if the fields that take part in the index expression are modified.

It's as if the grid is imposing yet another layer of buffering on top of hte VFP buffermode 5.


I thought I could fool it with GO RECNO() but no luck.

It needed skip, skip-1, thisform.grdAbbrev.refresh() in a custom method of the form [ I used fudge() obviously ] and then that method has to be called form the valid of Text1 of every column.


That "fixes" the problem. Sledgehammer and nut - but it stayed fixed.


I found without this with data like:

ASSCSVC .......... 1
ASSCSVC .......... 2
ASSCSVC .......... 3

When I added a new value

ASSCSVC .......... 0

That worked and was in the right place.


Change the order value to 4 from its default, TAB out of the field and nothing happens. Navigate and nothing happens. Scroll the record off the grid viewable area and scroll back and it's in the right place.
That led me to Refresh() - and to a really nice bug.

Set oRef to the grid, OKL F2 oRef.refresh()

Change the 4 to 0 and tab out of the field.
Press F2 and watch the grid duplicate records 1,2,3 beneath the record now containing 0 !!
Press the down arrow and watch the focus move *UP* to the record 1 above the 0, then down again to 2, to 3, to 0, and back UP to 1 while pressing the down arrow.

Press F2 again and having navigated from record to record the gris refreshes properly.


Change the 0 to 4 and tab out of the field.
Press F2 and watch all other records other than 4 disappear from the grid!
Navigate to the record bwlow or above and then press F2 and all is OK.

This was consistent no matter what record I added.