Edwin,
we have a similar problem. We are attempting tocall a FoxPro dll from .NET code and get a COMException. This exception only occurson some machines using windows server 2003. Curiously, some of our clientsusing windows server 2003 do not experience any problems.
We have searched the web and tried various things but still no solution. Thishas become a very annoying problem for us. Then today whilst considering calling the FoxPro COM object fromunmanaged code (VB 6), i came across this post.
I wonder have youfound a solution to your problem? Any help would be very very much appreciated, as at present i feel like i am banging my head against a brick wall with this one!!
SomeCodeMonkey.