Somebody please tell me I'm wrong here, and set me straight. WIth IIS6 (Windows server 2003) you can define an "Application Pool" and assign it to a web site, and in doing so explicity specify an identity under which the pool's threads run, correct? That's supposed to an improvement in IIS6 vs IIS5. This means that with Active Server Pages, your ASP scripts and invoked DLL's are supposed to to run under the specified identity of the worker-threads so you can really control "who is who", and not run into brick-wall permission errors when, for example, your ODBC driver tries to access a database from within ASP. In my experience, the VFP ODBC driver works just fine this way with IIS 6. However, I have discovered that the VFP OLEDB provider apparently does not. Instead, it runs under the IUSR identity. Why? This seems like a major bug, and it contradicts a primary purpose of having application pools. Isn't there some way to explicitly specify the identity under which the VFP OLE DB provider is supposed to run?