Wrox Home  
Search P2P Archive for: Go

  Return to Index  

asp_databases thread: ASP and Access Linked Table Problem


Message #1 by "Larry Hutson" <hutsonl@s...> on Tue, 23 May 2000 21:16:38

I'm currently working on a project that uses an Access 2000 database with 

links to tables maintained by an IBM AS/400 server. I'm designing this on a 

laptop, so I'm using PWS to emulate a web server--I have yet to field the 

system on an actual web server. I have a DSN configured to connect to the 

AS/400 library where the data resides. The DSN works when I invoke queries 

or view tables through Access, but not when I attempt to use it through my 

ASP pages.



Basically, I can run a query stored in the Access database and get results 

from the linked table.  However, when I invoke the query from an ASP file, 

I get the following error:



Microsoft JET Database Engine error '80004005'



ODBC--connection to <DSN name> failed



When I try to access the AS/400 directly (not desirable for this project, 

but worth trying to solve the problem), I get the following error:



Microsoft OLE DB Provider for ODBC Drivers error '80004005'



[Microsoft][ODBC Driver Manager] Data source name not found and no default 

driver specified



I keep thinking my PWS isn't configured correctly, but I've been unable to 

find a solution on MSDN.  Any help would be appreciated!



Larry Hutson

Message #2 by ckoski@w... on Wed, 24 May 2000 07:31:34 -0400
Did you see if your permissions were out of whack?  Maybe you need to add a

username and password to your DSN to authenticate yourself to the AS/400?  I

don't know much about AS/400s, so I'm just guessing now...



Another thing would be to check your connection string, and see if you are

indeed passing the connection string you are intending, because sometimes a

slightly misspelled DSN could cause your trouble without you knowing it...

try response.write'ing your connection string before you issue the connect,

so you can see what's happening...



**************************************************

Cory Koski

Website Programmer

Wabang Creative Technology

Brainbench e-certified Master ASP programmer





----- Original Message -----

From: "Larry Hutson" <>

To: "ASP Databases" <asp_databases@p...>

Sent: Tuesday, May 23, 2000 9:16 PM

Subject: [asp_databases] ASP and Access Linked Table Problem





>

> I'm currently working on a project that uses an Access 2000 database with

> links to tables maintained by an IBM AS/400 server. I'm designing this on

a

> laptop, so I'm using PWS to emulate a web server--I have yet to field the

> system on an actual web server. I have a DSN configured to connect to the

> AS/400 library where the data resides. The DSN works when I invoke queries

> or view tables through Access, but not when I attempt to use it through my

> ASP pages.

>

> Basically, I can run a query stored in the Access database and get results

> from the linked table.  However, when I invoke the query from an ASP file,

> I get the following error:

>

> Microsoft JET Database Engine error '80004005'

>

> ODBC--connection to <DSN name> failed

>

> When I try to access the AS/400 directly (not desirable for this project,

> but worth trying to solve the problem), I get the following error:

>

> Microsoft OLE DB Provider for ODBC Drivers error '80004005'

>

> [Microsoft][ODBC Driver Manager] Data source name not found and no default

> driver specified

>

> I keep thinking my PWS isn't configured correctly, but I've been unable to

> find a solution on MSDN.  Any help would be appreciated!

>

> Larry Hutson

Message #3 by "Larry Hutson" <hutsonl@s...> on Wed, 24 May 2000 15:28:17

Actually, the DSN (to connect to the AS/400) is part of the linked table in 

Access. I can view the contents of the table fine when I'm in Access, so I 

know the DSN is OK. I also checked the DSN-less connection I'm using to 

connect to the Access database itself, and it's OK. Is there some kind of 

problem with having two connection objects like this?



Thanks for the suggestions!

Larry


  Return to Index