>Greetings all!!
>Been a while since I posted (thankfully;))
>
>Well here's my current project: We're running a program using VFP6.0 and we're getting data corruption...now we know it's probably got something to do with the network, but it's becoming hard to find...so I'm wondering if there isn't some way in which we could trap this problem with code until we fix the network situation...???
>
>The problem, in more detail, is this: A worker is filling out these custom jobs, and he does like 50 at a time, then they're all saved. Now when he does this it will, many times, corrupt the indexes and then everyone that's using that program has to get off it and the databases are re-packed, which fixes the prob...until it happens again. The fun part is that there is no real error dialogue that shows up...just the standard foxpro box:
>
>
>Prorgam Error
>
>Error reading file.
>
>
>Cancel Ignore Help
>
>
>Clarification: This is NOT a program created by us, but the company which made this program is telling us this is a network error, now while that may be true...you'd think they'd put some better error handling routine in effect to catch this and report more clearly on it...anyone have any suggestions?
I've sen Error Reading file when the workstation lost connection to the network. After changing NIC and motherboard, we narrowed it down to bad wiring. Unfortunately, this is a very difficult problem to track down.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer