Previous Topic

Next Topic

Book Contents

The Wrong global.asa

I have seen cases where in changing the database connection in FrontPage 2000 from a System DSN to a direct connection to a database file in the current web or vice versa, where FrontPage replaces the SF2K global.asa with a default copy of global.asa, which does not contain the special SF2K code required.

If you suspect this, you should import a fresh copy of the SF2K global.asa file from the StoreFront template files and recreate your database connection in FrontPage 2000 and verify it. That should correct this particular problem.

To see if your global.asa is the wrong one, you can open it in HTML view in FP2K and scroll down and look for these lines:

Session("DSN_Name") = Application(appDict.Item(0)) ' Requires FP 2000 Extensions

'Session("DSN_Name") = "Your DSN Name Here" ' Use for FP 98 Extensions

DSN_Name = Session("DSN_Name")

If you don't find these lines, if is not the correct global.asa file.

See Also

Other Tips & Tricks

8004005 Errors

Updateable Query?

DSN & global.asa

My global.asa Doesn't Fire

I Can't Browse to my DSN

Short DSN in SSL Folder

An E-Mail Trick