Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

"Unable to Process" Error message

Status
Not open for further replies.

rohbe

IS-IT--Management
Aug 30, 2001
76
US
I am getting some strange error messages in an 2.6 application. The messages are either "UNABLE TO PROCESS ERROR" or "!g CTRL+F10" or "!y". These errors are intermittent and might occur every 10th or 20th time running the code. The code is being run under Windwos 95 on a Novell 5 network.

I have verified that these errors are actually generated by the FOX26 ESL file and not from an outside source.

This is a networked application with multiple users in at any one time. The code that this is occurring on appears to be a scan where I change the data in one column of a table. Instead of using a REPLACE all which requires a Table Lock I do the following

SCAN
IF RLock()
REPLACE nQty WITH 0
ELSE
=Delay(5) &&Wait 5 seconds
IF RLock()
REPLACE nQty WITH 0
ENDIF
ENDIF
UNLOCK
ENDSCAN

Thanks

Jean
 
I think you're hving some network delays. Do a search on network or novell in this forum and you'll find a bunch of stuff to tweak.

Dave S.
 
I agree it may be network delays, I had a similar thing with fpw26 on a nt network, and as you, had a 'replace all' that i chucked and used instead a 'scan... endscan' loop.

Also I found that my fpw26 application performance deteriorated very quickly (and problems increased dramatically) when 2 things were happening on the server.

(1) the server was near capacity (18gig with only 2gig free), and (2) was heavily fragmented, so we archived heaps of files (to give us 5gig free) and ran defrag and the problems went away.

Although foxpro was coping with what we presented to it (in terms of a vastly under maintained server), it appeared to users to be very sluggish. When we fixed the server problems, the fpw26 problems went away without tweaking one line of code.

Hope this helps


Pete Bloomfield
Down Under
 
Thanks for the advice, I have always considered the server suspect as well as that some of the problems may rest with Novell. Thanks again

Jean
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top