A few month ago, in an unrelated discussion, someone mentioned an instance where they were inserting a pause in their code to keep VFP from going to the next step before it had completed the last. I believe that they had put something like an INKEY(0.1) in the code. Can anyone expand on this problem or workaround?

I am working with a commercial accounting system that sometimes batches transactions such as shipping sales orders. It gathers up all the shipment info for from 1 to 1000 orders and then ships them all at once in a tight loop updating dozens of tables with each pass. More since they switched to VFP from Foxpro for Windows, we are running into problems. The system will come up with various errors, many from Windows, but the most common is "Drive K:\ not found" or "not available" or something along those lines. This always happens during larger quantities or orders and has only happened once while I was on site. At that time, I was able to switch to a Dos window and the drive was still mapped and available on that machine.

The workstations are always Win95 or Win98, never NTWS. It has happended on Novell networks and NT networks. I have gone through many OS tweaking exercises with no success. The only thing that helped a little, was to insert a wait window with a status update and a 1 second delay on each pass. This helped, but did not eliminate the problem.

Thanks for any thoughts,

Bill