I don't know. I don't think so. Here's what's doin'.

I am using a VFP8 DBC. I have an external .prg containing all the stored procedures I need. I created a C# class that pulls data from the DBC (via stored procs only), and with the XmlTextWriter I create an XML string that it returned to any caller.

The C# class is a .DLL which I am using as a private assembly in an ASP.NET app. I have two ASP.NET pages that both do this:

DataAccess dataAccess = new DataAccess();
string xmlStuff = dataAccess.GetMetaInfo(indexKey);
Trace.Write(xmlStuff);

I build the project in VS.NET (CtrlShiftB) and then open an IE session to hit my frames page that opens both ASP.NET pages. Sometimes I get "access denied" on the external DLL and either one or the other or neither will load. So far this has only happened with me on VFP, not MSSQL (have not tried Access or Oracle or etc).

I can't consistently reproduce why I get "access denied", but I do get it from time to time. My remedy was to create two DLLs that do the same thing, one for each ASP.NET page, and also create a "retry-try-catch" block in my pages that use my DataAccess class, give them each 20 seconds to re-get the XML and then fail. That's not where I want to be at all, but it's letting me continue to develop while I try to figure out why this is happening.

I'm on the "is VFP OLEDB thread safe" question because I think the .NET XML classes might not be (I'm not sure), but I want to check out any and all reasons why my data fetch/provide class is not as solid as it should be.

Thanks for any thoughts.


>>Is the OLEDB driver free-threaded?
>
>Yes.
>
>>I am doing some stuff with ADO.NET and sometimes I get "access denied"
>
>As with any multi-user environment is file contention a possibility?