Further to previous reply, I've just tested a new version of Y2kFoxW direct from the developer which does indeed seem to fix the CPU utilisation. It'll be running live in a 70 user environment from Monday. We've had no other problems with this product at all.

I now reckon that this is a *great* third party fix for the Y2k on Foxpro for Windows. I couldn't imagine that I'd want more.