>>>>We are developing a web site using VFP5 on a NT4 machine using IIS3 as the web server. This
>>>>NT machine is also connected to our Novell file server.
>>>>
>>>>We are also using a few Active Server Pages(ASP) to access our VFP tables.
>>>>
>>>>We are having a problem using ADO to access a VFP free table that reside on the
>>>>Novell file server.
>>>>
>>>>Our ASP page tries to query the VFP table using ADO to talk to the ODBC data source, but
>>>>the web server generates a message saying that the table is not found.
>>>>
>>>>However, if we copy the table to the web server's hard drive and redirect the ODBC
>>>>data source to that file, the ASP page and ADO works just fine.
>>>>
>>>>Can ADO talk to a ODBC data source that resides on a Novell file server?? The user rights for that
>>>>machine does have rights to do this, but we can't access the tables on that Novell drive
>>>>using ASP ans ADO.
>>>>
>>>>Jerryt
>>>
>>>We have the same problem and have been working with MS for a while on getting it fixed. We have no resolution at this point because we have been very busy with other problems and we are working around by bringing what we need down to NT local. MS says they have a fix but I beleive that it will include moving to the latest Intranetware Novell and I'm not sure Our IS department is ready for that. If you find an answer please let me know.
>>>
>>>Jeff
>>
>>We also ran into the same problem and have been awaiting an fix or workaround from Microsoft for a few weeks now. Apparently they don't have one yet.
>>
>>Sean
>I know that it's not quite the same environment as the one you are writing about but this sounds very similar
>to I problem I encountered. I am using the FOXWEB CGI componenet with VFP in a NT and Netware environment.
>The Data files reside on the Netware server. When I ran FOXWEB as an NT Service I got an error "could not open tables".
>All the security was OK. It took a while to figure it out!! The problem was that when an NT service ( FOXWEB, Or
>even MS ASP ) opens a file on a netware server it cannot open it using a DOS drive letter, it must have the full
>server path to the file. So opening f:\data\app.dbc , where f: is a netware drive, will not work,
>but \\netwareserver\data\app.dbc will work. It has to do with it being a service and problems with
>the netware client.
>
>So my suggestion for you is to make sure the ODBC entry for your tables does not have an entry that uses
>a drive letter but uses the full server path.
>
>Let me know how it worked out,
>mikeb@advbustech.com

Been there. Done that.
Thanks anyway !
Jeff Butler