Thanks.

I tried pasting it into Fox and it crashed, but noticed the line number in the call list refers to a line in our code with 'evaluate()'. I've seen this before.

Evan Delay suggested I report this to MS and will do so. Yes it is outside FoxFire!

We initiated the 'evalute' code to avoid some re-entrancy problems i.e. the cursor is closed by another 'thread' before the current one completes. We don't want to go back to the old code, but the code with evaluate and SP3 doesn't work on large result sets either.

What we will do is write a small Fox program and fiddle with our function. First check that it fails, then take out the call to 'evaluate' and see what happens.

If you have any other ideas, we'd appreciate them.