Access 2000 Database connection not defined

[ann_nyc]

I have been hunting around and trying a number of KB
articles - I will list them later - but I cannot display
database results in my web page.

Here is the situation. I built the website in FP 2000. I
have a few .asp page in the site meant to connect with a
database created in Access 2000.
I inserted the database results on a page within my web
and was able to successfully add and verify the database.
I have IIS 5.0 installed and configured on a Windows 2000
box with the FrontPage Extenstions for testing.
I have published to a subweb in the wwwroot and everything
looks to be in order. Everytime I call a page that calls
a DB I get the following:
Database Results Error
The database connection named 'database1' is undefined.

This problem can occur if:
* the connection has been removed from the web
* the file 'global.asa' is missing or contains errors
* the root folder does not have scripting permissions
enabled
* the web is not marked as an application root

The connection has not been removed, I have renamed and
then "recreated" the global.asa file as per a KB article,
the root folder does indeed have scripting permissions
enabled and the web IS an application root.

ASP seems to be functioning properly as I am able to
execute various scripts. I have tested this a number of
different ways and I have been successful each time. The
problems seem to start when I attempt to connect to a DB,
any Access DB I have created and I have created and tested
a number of them.

I have tried these KB articles for a solution, but none
has resolved the issue: 219170, 232612, 265323, 265174,
204152, among others.

The most telling one was 265174. The article says that if
the =Application() variable returns nothing (which it
did), one of the following conditions is true:
The Global.asa file is not being executed; this is
probably because of the folder not being configured as a
program.
The Connection String in the ASP code is not defined in
the Web settings.

It refers me to another article, but this does not resolve
the issue either.

Does anybody have any ideas?

Thanks, Ann

 

[Jim Buyens]

Your Web is probably not configured as an application in
IIS.

To fix this:

1. Open the virtual server in IIS Manager.
2. Right-click the root folder of your Web, and
choose Properties.
3. Make sure the Directory tab is selected.
4. Under Application Settings, click Create.

You may need to delete and recreate the database
connection after making this change.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------

 

[ann_nyc]

Thanks, Jim. This was one of the first places I looked.
I removed and created the application name and recreated
the database connection, but I still have the same issue.
I tried this again for good measure and the issue is still
not resolved.

Any other suggestions?

Thanks,
Ann

 

[Kathleen Anderson [MVP - FP]]

What does the database base connection string in the global.asa look like?
You can open the file with Notepad - the connection string would look
something like this:

'--Project Data Connection
Application("fpdbwndbc_ConnectionString") = "DRIVER={Microsoft Access
Driver (*.mdb)};DBQ=URL=fpdb/FPNWIND.MDB"

 

[ann_nyc]

I had looked here some time back, but I must admit, that I
don't know much about this file so I can't say that I knew
what I saw. It reads:
'--Project Data Connection
Application("team_ConnectionString")
= "DRIVER={Microsoft Access Driver
(*.mdb)};DBQ=URL=team.mdb"

But it is wrong. The path should read
DBQ=URL=fpdb/team.mdb"

I have recreated the global.asa twice now by renaming and
then re-establishing the database connection, but my
results remains the same. I have even moved the database
to the root - not where I want to keep it, but for testing
purposes - and I get the same results.
Should I edit this manually? If I do, are there any
changes that need to be made to the ASP files?

Thank you for your help,
Ann

 

[Jim Buyens]

I had looked here some time back, but I must admit, that I
don't know much about this file so I can't say that I knew
what I saw. It reads:
'--Project Data Connection
Application("team_ConnectionString")
= "DRIVER={Microsoft Access Driver
(*.mdb)};DBQ=URL=team.mdb"

But it is wrong. The path should read
DBQ=URL=fpdb/team.mdb"

I have recreated the global.asa twice now by renaming and
then re-establishing the database connection, but my
results remains the same. I have even moved the database
to the root - not where I want to keep it, but for testing
purposes - and I get the same results.
Should I edit this manually? If I do, are there any
changes that need to be made to the ASP files?

I would say that yes, it's OK to make this change manually.

If that works, it would be interesting to open the connection
via Tools, Web Settings, Database and see what appears. (Don't
save, though, unless you're feeling adventurous.)

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------