>Justok,
>
>You are absolutely right. My solution assumed a cursor ... and it that case you might as well sort it properly and use the original strategy using recno().
>
>Can't blame me for trying :(.
>
>Regards,
>
>Marc

---

Hee hee, I seldom blame ppl. :)~~

I just try to give a worth consideration on cases to be concerned!!

In my previous post, the most value thing is NOT the coding part.
This is the possible cases to consider need to recall the code to get it right!

Actually, it always make me headache because some of coding may be called twice or more times for user simple one action!

The Net of Procedures call will make many cases... >:0

e.g. if try to assign a textbox value, a Side effect on textbox.programmicchange will come... So, if there is some code at that procedure....
a Chain of action doing that may not wanted!! *_*'

This Problem will be more serious in VB4.
Since there is only one procedure named: Change() which consider both interactive and programmic, the trouble make me Cry... ~>_<~

Unexpected Loop may be come out or Sereval Task will ReDone again and again!

---

Back to topic, I still advice Gilles Not to make color on row!
Since grid.beforerowcolchange() and grid.afterrowcolchange() are always Called,
it will make it very slow!

My Coding Advice:
Try to make code call Only once as easy as possible,
Else if recall two or more times, it will easy get out of control!! Beware!