>>How would I start using the library in that case?
>>GetProcAddress? Anyway, as soon as I call FreeLibrary(handle) in the Unload...Do I need to tell you? :)
>>
>>No I don't cause, *poof* and there goes another instance of vfp7.exe! My eventlog has trouble keeping up with this rate.
>>
>>I can reprocedure the problem on Win2K, so it's not just WinXP either....
>>
>>On the other hand, I have trouble establishing whether I still have local variables, as soon as I skid past the last ENDIF (see code in previous message) both the lnArcHandle and lnResult are gone. My debugger 'speaks' of only one object remaining and that's my form....
>
>Did you ever manage to solve this problem?
>We have the same issue with - yes - a 3rd party dll

I'd try to wrap accessing/using the 3rd party dll within a separate process
- preferably within a VB6 exe, which is then allowed to go poof.
If you want to reuse existing vfp code and work through a vfp.exe,
Do not call via activeX for first try,
but instead through the venerable old 16-Bit Windows calls already found in FPW.

my 0.05€ (been there, also crashed...)

thomas