I think you're right. The line of code seems to be somewhat random - this was the line of code referenced by just the most recent occurrence of the problem.

>Just a thought, If your other C5 issue is related to the C5 code that I have and mentioned in your other thread, MS support told me that the code I submitted to them caused memory to get corrupted. If that is the case, VFP could cause a C5 on any line of code and it could be coincidence that it failed on that one line of code.