Re: Unable to access Access DB via ODBC under IIS under WIN2K

Try to give full permissions to IUSR_MACHINENAME for the directory where the Access DB resides. This worked for us (IIS4/PHP4.x) Christoph "Bill Seeley" <bseeley@comcast.net> schrieb im Newsbeitrag news:20020205235002.21905.qmail@pb1.pair.com... | I already have a working ODBC DSN for the database that is accessible from | both the API version of 4.1.1 PHP under Apache and from Crystal Reports. My | problem is that I can't access it from PHP (CGI or ISAPI versions) under | IIS. | | "Nicole Amashta" <430ntr3k@bellsouth.net> wrote in message | news:20020205150421.24223.qmail@pb1.pair.com... | > You must set up the ODBC source you want access to. Go to control panel, | > administrative tools, ODBC ... (if you haven't done this already). | > | > Go to the DSN tab and create a new datasource there. Are you familiar with | > this? | > | > If you need further help setting up an ODBC source, let me know. After | > creating this source, you can then use it through your PHP scripts. | > | > hope that helps any. | > | > ~Nicole Amashta | > www.aeontrek.com | > | > | > "Bill Seeley" <bseeley@comcast.net> wrote in message | > news:20020205131942.51944.qmail@pb1.pair.com... | > > When attempting to query an Access 2K DB with the odbc_connect function, | I | > > get the messsage: | > > | > > Warning: SQL error: [Microsoft][ODBC Driver Manager] Data source name | not | > > found and no default driver specified, SQL state IM002 in SQLConnect in | > > e:\vnpweb\html\getcontact.php on line 14 IM002 | > > | > > I have tried both the CGI (installer version) and ISAPI versions of PHP | > > 4.1.1 (manual install) and get the same messages. I am able to access | this | > > same data source name with Crystal Reports and was previously able to | > access | > > it with a PHP script under an Apache server (php4apache.dll version) on | > the | > > same machine. I've enabled both ODBC and PHP logging, but PHP logging | > > doesn't give me any more than the above messages. Curiously the ODBC log | > is | > > empty, even though the above messages would indicate that the MS ODBC | > driver | > > returned a legitimate error code. | > > | > > Has anyone seen anything like this and can you offer any suggestions? | > > | > > Thanks, Bill Seeley | > > | > > | > > | > | > | |