Database results Wizard error

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am using an ASP page to *try* to display results from a SQL Database.
Everytime i use the wizard it throws the "Database Results Wizard Error". Ive
tried the following:

- Specifying a username and password in the Database tab in site settings
- Installing Service pack 2 for office.

Really at a loss on how to fix this, if someone could either tell me how to
fix the problem or point me in the direction of somewhere where i can find
the asp code to do this.
 
To see the true error from the DBRW , open the hidden folder /_fpclass/ and edit the fpdbrgn1.inc file
At about line 19, change :
fp_DEBUG = False
to :
fp_DEBUG = True


_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
_____________________________________________


|I am using an ASP page to *try* to display results from a SQL Database.
| Everytime i use the wizard it throws the "Database Results Wizard Error". Ive
| tried the following:
|
| - Specifying a username and password in the Database tab in site settings
| - Installing Service pack 2 for office.
|
| Really at a loss on how to fix this, if someone could either tell me how to
| fix the problem or point me in the direction of somewhere where i can find
| the asp code to do this.
 
Use Tools Sites Settings Database to Define or Verify your DB
- it should generate a global.asa listing the connection (that is what FP DBRW uses)

--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
_____________________________________________


| The True error is
|
| - the Database connection named "xxxx" is undefined
 
There is a global.asa file present but i couldnt tell you whether or not its
correct. All the obvious things seem to be ok - the project data information
seems to be correct.
 
Have you checked with your ISP to make sure that the connection string is
right? Or are you using a system ODBC DSN?
 
Is the SQL Server on the Virtual PC as well? When you make your ODBC
connection is it to "localhost" and is SQL Server running? Are you doing all
your work and testing from the Virtual PC? Can you do a test with an MS
Access database to rule out problems with SQL Server? Are you able to test
this on another PC not running Virtual PC to see if that's the issue?
 
Back
Top