Nope same issues if you're talking to a VFP database... OleDb is subject to the same permission issues you have with a COM object or other mechanism. You can do this *if* you log in first (ie. NT Auth on a page), but on a shared server you're unlikely to get the ability to do this either.

Fox Data sucks that way on a Web server because you're dealing with physical files in the OS file system. SQL Server (or other backend) of course don't have that problem because the security is completely separate from the file system.

+++ Rick ---


>One of the reasons I've been reluctant, or even unable, to move away from the more expensive model of leasing a dedicated server for my hosting projects is the lack of admin-level access to the file system that is inherent in a shared hosting environment.
>
>I've found this admin-level access to be crucial when setting up new databases for my web apps. When I drop the new database files into their proper folders after creating them in FoxPro, they naturally don't have the proper file permissions to enable the web app to properly access them.
>
>If not for this limitation, I'd be able to consider moving to the less expensive model of shared hosting.
>
>So my theory is this: rather than use FoxPro to create the individual database and table files and then manually add the appropriate access rights, I should be able to use a standard SQL command executed from within an .ASPX page to do so, shouldn't I? Something like this:
>
>"CREATE DATABASE C:\Data\NewDatabase.dbc"
>
>And then:
>
>"CREATE TABLE C:\Data\NewTable (iID i PRIMARY KEY)"
>
>If my theory is correct, the new files would have all the correct permissions, as they were created by the web app itself and not an external process.
>
>Has anyone done this with an OLEDB driver -- create a database from scratch through ADO.NET?