'Cannot update cursor' problem

[aharrisreid]

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

 

[ramani]

Hi

It could be your NIC or a bad network connection as well.



____________________________________________
ramani - (Subramanian.G)

http://winnersoft.coolfreepages.com/

 

[aharrisreid]

Hi ramani,

>It could be your NIC

NIC? What does this stand for?

Thanks,
Alan

 

[Stella740pl]

Network Interface Card?

 

[aharrisreid]

Hi stella740pl

>Network Interface Card?

Thanks,
Alan

 

[Mike Lewis]

Alan,

I think your best bet is to get as much information as possible from your error handler ... not just the line number, but also the actual line of code, the name of the method or procedure it was called from, the current alias and record number, and anything else you can think of. Your error handler should be able to log all this information.

If the error always occurs at the same line on code, I would doubt that it is caused by a bad network connection. If it was, I would expect it to be more random. It's much more likely to be a problem with the code itself.

If there is any chance that you could temporarily install VFP on the offending workstation, you could try to reproduce the error while running in the development environment.

Hope you manage to get it sorted.

Mike


Mike Lewis
Edinburgh, Scotland

My Visual Foxpro web site:

http://www.ml-consult.demon.co.uk

My Crystal Reports web site:

http://www.ml-crystal.com

 

[aharrisreid]

To all who replied to my original message...

Solved the problem - the share rights on the data directory had somehow been changed from readwrite to readonly. Everything seems to be working ok now.

Many thanks,

Alan