ODBiC Discussion Board

RE: It does work now. However another problem prompted up, Ian, 01-10-2006

Database connection failed

by Roger Harris, January 11, 2006 00:40

What Dave explained to you is called "script mapping." If you followed those directions, then what you did was to tell IIS that whenever a URL references a file ending in .odb, it should run odb.exe to execute that file as a script. But if you do that, then you DON'T put the /cgi-bin/odb.exe in any of the URLs -- you just directly reference the .odb files the same way you would .htm files. All of the links in the example file directly reference odb.exe, passing the .odb file names as "path info" data following the /cgi-bin/odb.exe part of the URL, so unless you changed those URLs, if it's working now, then the script mapping can't be the reason; you must have fixed whatever the real problem was. (The only reason I mention that is that you'll probably find it easier going forward if you can understand why it wasn't working before and why it is now.)

Immediately before the "Error in file wwwtitle.incl line 20" is the only clue that you're going to get about what the error really was: it's the error message returned by the ODBC driver. Please, Ian, if you're going to ask for help here, you need to understand the importance of explaining *exactly* what you're doing and reporting *exactly* what error messages you're seeing. None of us are mind readers. Obviously, this is your first attempt at Web development, so it's understandable that there is a lot you don't know yet, but you need to learn to ask better questions if you want useful answers.

Assuming that the ODBC error you're seeing is a connection failure, there are a couple of possibilities. One is that the file you specified in the DBQ is not found, and again, that could either be because the DBQ reference is not to the correct directory and file, or because the .mdb file isn't really on that directory. (You can use either "/" or "\" in file paths, so that's not the problem.) The other possible reason is that your XP system is not allowing CGIs like odb.exe to open a database using a "DSN-less" connection (i.e. one where you directly specify the file with the DBQ and the also specify the driver). If that's the case, then you need to use the ODBC Manager program to set up a System DSN, and then you need to put your DSN name in the DATABASE statement -- take out the DBQ and DRIVER keywords and add the DSN=... keyword. All of this is explained in the Users Guide.


Post Your Reply:

E-mail  optional

HTTP Link: 
Link text: 


Copyright ©1997-2003, Roger Harris. All rights reserved.