>Would ther be a reason for a DLL to work for 6 months in one application and then suddenly fail in another?
>
>I have a C++ DLL that does some file handling functions for me. It has been working fine in my file parsing routines for months now. I needed to do something similar, so I LITERALLY cut-and-pasted(the VB method of inheritance) the code from the working routine and took out the lines I didn't need. The only things I changed were pathnames and such. Now, the thing totally blows up my (NT 3.51)workstation (completely exits VFP 3.0b or gives me the ever-so-helpfull "couldn't read memeory at..." message). I tried it from within VFP and as an exe, same effect. All 4 functions from the dll get registered, and it calls one of them fine, it crashes on the second call (I know it is failing here for sure, MessageBox(), the great debugging tool (s)).

Scot

Was the platform always Win/NT 3.51? Has anything at all changed?

Tom