My guess is that the app is trying to find things that are not there. So it's traversing every folder it knows about looking for things.

A QA guy I work with uses all kinds of tools and he is always showing me my folder names in the VFP build I've done. I've also seen network scenarios where there is a network problem, causing the workstation to get disconnected. Occassionally at that point, an error message will display saying that it can't find a file, and one of my folders will be in the path it displays that it can't find.

>We have an application that has been in existence for the last 7-8 years. The code has evolved from the DOS version all the way up to VFP-8 SP2. We have one client that is experiencing network slowdown of the app.
>
>The clients IT department has conducted network sniffer tests and they reveal that the application (executable compiled) is making IO calls to directories that exist only in our development environment for example.."/libs,/progs". The actual application when installed does NOT have these directories.
>
>Can anyone explain why a compiled executable distributed would have these sniffer results that are displaying our development environment?
>
>Wayne Frenck