Hello again,

We're pretty sure this has to do with the .Net 3.5 framework. You mentioned that the framework probably changed a dll.

You also mentioned that if it were a dll change, then that would be difficult to figure out. Do you have any plans of updating vfp.fll to work with the .Net 3.5 library?

If not, do you know of any other programs that will do what vfp.fll was doing in providing a callback handle to a VFP function?

Thanks for your help!

Rodd

>>Hello Gregory,
>>
>>We've been using your vfp.fll callback routine for some time now to implement a progress bar when using a zipping dll. However, our wrapper routine now crashes when I run it from my station. The routine works fine for everyone else.
>>
>>The only thing I can think of that accounts for the difference is that I have loaded Visual Studio 2008 on my machine. I'm wondering if this has updated some sort of external C dependancies that keep vfp.fll from running on my machine.
>>
>>Are you aware of any such problems or can you think of anything that would keep me from being able to load the library?
>>
>>Just for clarity, this is the error message I'm getting:
>>
>>The line of code (even if I try this from the command window if fails)
>>

set library to vfp.fll additive

>>The error message that I receive is that the library vfp.fll is invalid.
>>
>>Thanks for whatever help you can offer.
>>
>>Rodd
>_____
>
>Rodd,
>
>Two things I can think of
>(1) dependency walker - as suggested
>(2) You may want to recompile the c-code. It was compiled with the vpp6 api's. To be honnest I do not know whether that will help.
>
>(2) may not be the solution to your problem. I suspect vs2008 (having installed the 3.5 framework) may have changed a dll - but that is hard to tell
>
>Success,