>>
>>You would use a UNC path instead of a network share name. I think you had that in your first message. They usually start with \\servername.. etc.
>>
>>For share names and virtual directories you would still need Server.MapPath(). Setting Web server permissions is not a walk in the park, so be ready to do some trial and error with the NT / Web server permissions.
>>
>>Also, try using a system DSN on the web server.
>>HTH
>
>I put a html file on the database server and I had no trouble running it on the web server. In VFP I can do ADO stuff connecting to the database server, therefore the permissions should be okay.
>
>In ASP I tried the following and nothing work:
>Data Source = \\dataServer\d\tastrade\tastrade.dbc
>Data Source = http://virtual root/tastrade.dbc
>Data Source = /virtual root/tastrade.dbc
>
>wwwroot
> |______virtual root
>
>My ASP file is in wwwroot
>
>I receive this error
>Error Type:
>Microsoft OLE DB Provider for Visual FoxPro (0x80004005)
>Invalid path or file name.
>
>Please Help

That would imply that the database file is not being found. Try to get at a valid file name first by testing with the FileSystemObject object. Something like:

Set oFSO = Server.CreateObject("Scripting.FileSystemObject")
Response.Write oFSO.FileExists("\\myserver\sharename\folder\sus\myfile.dbf")

You might also want to test permissions with:

Set objPermCheck = Server.CreateObject("MSWC.PermissionChecker")
Response.Write objPermCheck.HasAccess(sPath & "\" & sFile)

Where sPath is a physical path. FWIW, opening the connection through VFP uses different permissions than if you use the connection through the Web server. The first uses your NT permissions and the second uses the IUSR account.