>>We also encountered the exact same issues and what we found was that it appeared to occur most often with sequential drives going beyond D: (A,B,C,D,E). When we remapped the "D" drive to something else, the issue would go away.
>
>I have quite a few drive letters on my machines - the real HD letters usually top out between J: and M:, and the physical HD's range from 2 to 5 from PATA via SATA to SCSI. What I almost automatically do is remap the CD/DVD writer to W: and an accompaning CD/DVD-ROM to V: - that is just to not fumble when going back to dos prompt or batch files. The USB drives each get a fixed letter (U:, X:, Y:) and a RamDisk is always Z: if in use, and only one machine still has a B: (with 5.25'). This takes a bit more time to set up (including double to triple OS partitions for multiple boot and sometimes special "fast" partions on the outer rim of the physical disks) but gives you a very responsive system since your "workspace" is always on the fastest area and this can be either defragged or quickformated, while the large spaces needed for medium time storage is taken form the slow disk areas. Perhaps that "saved" me from the things you describe <g>.
>
>But even on the "otherwise-administered" machines I never ran into this in vfp unless you count a botched registry from an install before a remap. (And I *told* the yerk before what would happen).
>
>I also have in my "scripting island" of 6 very high powered machines remapped 2 partitions to higher disk letters (S,T) and set them up as network drives on all other machines and as default for most vfp activity. Much less pain than synching always via SSafe, as we check in only for "real" milestomes and/or backup fallbacks and not any more just to update other machines. No real problems yet, but here I am somewhat hesitant to call it "stable" - must get more data *and* we are only 2 developers working allowed on the island.
>
>Have you checked with the debugger what lines prompt the error ?
>
>curios
>
>thomas

No, I haven't. The problem only happens on one computer at the client site. The other 3 pc's show no such problem, and all the machines are supposedly configured alike. Their IT department doesn't like other people messing with their machines, and they are looking to see what might be different about this one pc, but I haven't heard anything from them yet.