>>As to your suggestion: It sounds on target and fully in keeping with the joy of maintaining legacy code. Unfortunately, from this end, my Fox app appears to use its existing CDXs correctly, so I'm not sure if the 'destroy and rebuild' approach will work in this case. Still, I hate to give in so quickly to a problem without knowing it's true causes, so I'll pull out the earlier version of my utility, try your idea, and post my findings.
>>
>>
>>Regards,
>>Jim
>
>Jim, no problemo. Yeah, I has to use this technique and it ALWAYS works. It totally solved my problems.


>
>Let me know how it turns out.

Carl, Argh. No joy. I killed off the CDXs and rebuilt them on the NT box, ran an old version of my utility, and got the same visit from Mr. C0000005. I tried this on some different data groups, thinking I might have a corrupt DBF, with the same result. I'm wondering now if the problem might not be with the Foxpro ISAM driver running on NT (it runs swell on WIN9x). If so, I'm afraid I'm not technically advantaged enough in that area to go further. :(

I'll keep researching, but the workaround I used has kept me floating.

Thanks again,
Jim