Hi,

It sounds as if your making this overly complicated. VFP installation / configuration on client machines is irrelevant. If you have VFP installed on the production web server can you use the COM object from that? If so the problem is likely a permissions one. What other attributes did you set in the Web.config identity tag ? Where is the data located ?

Regards,
Viv

>
I have created an OLEPUBLIC class to access data from Fox or SQL tables, to be used in an ASP.Net application. The purpose is to reduce the lag incurred by large datasets returned prior to filtering.
On my 2 machines (XP), and our test web server(W2K), I can instantiate the object and call the methods without issue. In VB, VB.Net and ASP.Net.
On two coworkers' machines(W2K), the object won't instantiate, in any of the mediums above.

On one of their machines, I actually installed VFP 7 to shortcircuit the error, to no avail. I can compile the code there, register the component and run it in VFP. Once added to the ASP.Net page as a reference, the methods are available, and the parameters stated. The .Net wrapper seems to be intact, therefore. But, load the page, press the button and the instantiation hangs.
I created an install CD using Install Express, and installed in on the other coworker's machine. It completed successfully, and again, adding the reference made the object available normally. I included the runtime files for VFP, as well as the ODBC driver, for later use.

I changed the impersonation statement in the web config. to true, based on some reading I had done of other people's problems. It didn't help.

What am I missing here? I am sure it is simple and obvious!
>