Hi,
Do you using the same versions of fll's with VFP5 and VFP6? If "yes", then it's your problem. Fll's must be recompiled for each VFP version using "pro_ext.h" and "winapims.lib" for this version.

>Basically I am working on the development of a commercial matching and sortation software package and am about 2 months into my present employment. I have inherited a fair bit of code and one thing which I have noticed is that there are two builds of the product one VFP5 and VFP6. I have discovered if the VFP5 build is used on NT or 2000 it either causes a GPF or hangs the machine and so the developer at the time decided to go back to the VFP5 build which seemed to fix the problem.
>
>I have never come across anything like this before and in as my first major development step I need to find these errors and hopefully confine all development to one project.
>
>I mentioned the ffl's earlier. I am not sure about these in the code and about how they are called or managed. The errors occur around these calls as reported by our users, but I have struggled to recreate this myself. Basically what I am looking for is a secure way to manage the fll's in the project and to call and release them in safety without compromise the application stability.
>
>Another related problem is the office toolbar which cause the application to hang, but unfortunately this is outside the scope of my limited knowledge...
>
>Bit vague I'm afraid, I need to discount each programming aspect in turn to try and get this to workout. Have you had any experience of this in the past.