James

No, one's Win98 (the broke one) and the other's Win2K. The 98 also has an issue with a label form (blue screen o'death), so I've quit working on this system on it. Unfortunately, I've been working on this particular machine for about 4 years now and the powers that be are getting ready to bring out the NT's (I mean XP's) on us.

If you want more weirdness, this grid also works on a co-worker's 98 machine - so it's obvious that it is a machine issue, at least as far as the non-firing events goes.

Thanks for the ideas...I'll give them a try.


>Dorris,
>
>I cannot understand how events that will not fire on one machine will work correctly on another. Are the OSs the same on both machines?
>
>The .ActiveRow property of the grid is, at best, fragile. The grid uses it for its own purposes, not for yours. The best course is to use RECNO( .RecordSource ). This will get you the actual row number.
>
>In my grids I add a .CurrentActiveRow property in the Init() method using .AddProperty() and update it with .CurrentActiveRow = RECNO( .RecordSource ) in the .AfterRowColChange() event. That way I always have a current row number without trying to depend on ActiveRow, which as you have found out, may or may not be accurate.
>
>Regards,