Guest_imported
New member
- Jan 1, 1970
- 0
Dear fox-collegues,
We work with barcodescanners on serial ports. To handle the data fast enough we read the ports with a lowlevel-routine, the serial input buffer cometmp.bin (written for clipper and foxpro). It is loaded by foxpro once(load cometmp.bin) and called many times per second in a loop to prevent for overrun of incoming data.
This solution generated networkcollisions, it seemed that foxpro sends a request to the network every time it executes a call cometmp . After putting
set defa to c:
call cometmp
set defa to
the extreme networkcollisions stopped. So the default path is involved.
We are puzzled, what can be the cause of this, why does foxpro have to look on his default network-disc (with cometmp.bin) when this routine was already loaded in the first line of the program?
Kind Regards,
Paul Jansen
Netherlands
We work with barcodescanners on serial ports. To handle the data fast enough we read the ports with a lowlevel-routine, the serial input buffer cometmp.bin (written for clipper and foxpro). It is loaded by foxpro once(load cometmp.bin) and called many times per second in a loop to prevent for overrun of incoming data.
This solution generated networkcollisions, it seemed that foxpro sends a request to the network every time it executes a call cometmp . After putting
set defa to c:
call cometmp
set defa to
the extreme networkcollisions stopped. So the default path is involved.
We are puzzled, what can be the cause of this, why does foxpro have to look on his default network-disc (with cometmp.bin) when this routine was already loaded in the first line of the program?
Kind Regards,
Paul Jansen
Netherlands