I have a networked VFP7 application (an .exe running with the runtime libraries). The application runs with no problems at all on the main file-server (let's call this pc1). However, on another machine connected to the network (pc2), I sometimes (about 1 time in 4 at present, but gradually increasing) get the error "Cannot update the cursor". As far as I can see there is no environment I can setup to cause the error to occur every time.

As I don't have the development version of VFP on the pc in question - I've temporarily modified the error handler to trap this specific error (111). So far I cannot trace the problem down to a specific line of code - the handler says the error occurs at line 0 (which I thought suggested the form.load event).

Looks like I'll have to make a client-site visit to solve the problem (I can log-in to pc1 via. pcAnyWhere, but cannot run the app. from pc2 - can I?). I'd like to prepare myself as much as possible, so I am trying to think how I can adapt the error handler so as to step-through the code from the previous wait-sate. I notice from the help files that ACTIVATE WINDOW DEBUG (or TRACE), DEBUG, are not supported in the VFP7 run-time libraries, so how can I follow my code?

I have tried running the app. on pc2 with and without the app. running on pc1, but it appears to make no difference to the problem. Unless it's a pc-specific memory or disc problem, I cannot work out why the app runs ok on one pc but not another.

Any help would be appreciated.

Alan