>Never seen something like this, but if you are distributing an exe, then

>you should md5 it so you can detect any change comparing with a saved md5.

>

>This way I've found viruses that changed parts of the code and antiviruses

>have cleaned them up, but leaving the exes in a different state than the

>original, sometimes even unrunnable.

That's a really good idea.

As it turns out, I'm embarrassed to say, the line of code reported in

the trace does exist, in a virtually identical list control subclass

on the same form (one overlays the other exactly). I wasn't paying

attention to the name of the control in which the error occurred.

There are actually 10 columns in the array in this method.

So what actually happened is that somehow, between:

FOR m.x = 1 TO ALEN(THISFORM.oMail.aSortList,1)

and

thekey = THISFORM.oMail.aSortList(m.x,10)

somehow the length of the array got truncated.

Now, there is NO other code between those two lines, so

ALEN(THISFORM.oMail.aSortList,1) would have had to return an

impossible result for the next line to fail.

I have seen this on a few occasions when iterating arrays, but I

remain mystified as to how it could happen.

Ken

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox

OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/F5.B6.16480.32E37B85@cdptpa-omsmta02

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.