Hi Marcus,

I ran into a problem when we converted from VFP 3.0 to VFP 5.0 with this as well. It turns out that any reference to the grids activerow or activecolumn properties if the afterrowcolchange event can cause this behavior, I believe this is fixed in 5.0a.