Yes. I did some checking and you're right. This fix is not about the border repaint issue. I assume Calvin's code does that, but again, you need to remember to fix the order of items in the property field whenever you save a form - new or existing.

I notice also that Calvin's code (I'd only use it as a one time run) only fixes the properties in an scx file, and doesn't do anything to the forms within a vcx file. I don't know whether it's necessary or not. I assume it isn't a problem with inherited forms, but I'm not sure about instances of those form class objects using createobject() and form.show()

>I beleive this fixes the highlighting issue in the listbox. Without it, this listbox behaves like you are multiselecting items as you move through the list.
>
>>I use this code in the startup program (I can't remember where it came from, but seems to fix border issues):
>>
>>IF VAL(OS(3)) > 5
>> DECLARE INTEGER GdiSetBatchLimit IN WIN32API INTEGER
>> GdiSetBatchLimit(1)
>>ENDIF
>>
>>>>Agreed, I thought SP2 was mostly about Vista compatibility. I've tried it on a laptop and desktop, and the bad behavior happens on both unless I turn off Aero. I'm astounded that they didn't fix this. What were they doing all this time? So now the best case is that I have to remember to run Calvin's utility every time I create a new form (thanks to him for the utility, though!)
>>>
>>>Also, any time you change a form. Saving an existing form will re-order the information in the properties field of the scx file.