>Sorry, forgot to mention: VFP6/SP5 Fox runtime libraries are dated 18-8-0.


In this case, the ususal procedure I follow is to debug, and try to find a bypass. You already did the debugging - or part of it. Why does val() fail? I don't know. Or is it the CASE statement that fails?

First of all, I would separate the CASE from the VAL(). You should also try to find out under what circumstances the command fails. This, of course, is the real challenge.

Hilmar.

...
>>We have a procedure that prints the contents of a grid. This procedures sometimes crashes with a C0000005 error, always on a line like:
>>
>>CASE VAL (luValue) > 0
>>
>>luValue is of type C (tested before this) and the crash cannot be reproduced. The next run might crash as well, but on a different row in the grid, or the next run does not crash.
>>
>>The printing itself is done through Excel Automation, but considering the line of code I'm not sure Excel has anything to with this.
>>
>>Has anyone experienced similar problems or have a solution for this?
>>
>>Thanks,
>>
>>Auke