If speed and performance are issues:
1. AVOID the SET FILTER function. Everytime it is invoked, it must scan the entire dbf to determine the records to include. The more records added, the slower the process becomes.
2. Use SET DELETED ON. It will make the deleted records 'disappear' without...
the nanfor library will require recompiling the program, right?
there are other options that I have used successfully.
If recompiling isn't desirable, let me know.
Boss is right on.
You may want to add some logic as to not read the same files over and over again, either by deleting the file once its read, setting the archive bit, or keeping track of the read files.
Good luck
Next time it happens, if you can get to the workstation quicky enough, it would be interesting to see if, from a command prompt you can do a directory of the server drive and "see" the file that the Clipper app couldn't find.
If the file is listed as part of the directory, but errors under...
I linked in a library that gives my Clipper code functions to run a scanner, like "scan" and "view" and "print."
works pretty slick and is seamless; no exiting Clipper app to run a scanner program, etc.
I had the lib developed for my own use and would consider selling you a copy. email me at...
I have had success with using DPAKBD.COM for the CPU/time slice problem. For those not aware, it does not require any Clipper recompile and drops 100% CPU utilization to about 40%, allows the rest of the apps to run like they should.
If interested, search for "DPAKBD" on www and download it...
Don't think a network sniffer will help you out with this.
Do you know at what point the index is getting corrupted?
You may need to narrow it down to the process thats corrupting it. Possibly rebuild the index, then check it after a few of the 20 minute updates to see if its corrupted. If so...
hello experts,
here is my problem...
have a group of users from a call center now on XP. They all have multiple applications running, minimize them, and click on the task from the task bar when they need one of them. A couple of the sessions are DOS windowed sessions started by the cmd...
check the CPU utilization when your Clipper app is running, when it's locked up, etc. If near 100%, then you need to slow the KB sampling down. If that's the case, there are solutions throughout this site. I use the DPAKBD.Com routinely to handle this.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.