Any particular reason why you wouldn't use an ADO DSNless connection? Then ODBC is not needed, it's faster, and it's more secure.
Info on DSNless connections & connection strings in general:
http://www.blueclaw-db.com
http://www.communitymx.com
http://www.carlprothman.ne
Of course you should have the database in it's own folder, and that folder will need additional permissions in order for the website to be able to read and write from/to it.
To follow the "microsoft pattern", the database folder should be "fpdb", and then you can use FrontPage to set the permissions of that folder automatically, without even having to use the server control panel.
Main Topics
Browse All Topics
by: RouchiePosted on 2006-09-05 at 06:08:05ID: 17455304
Usually there is an option to create the DSN in your account control panel. The DSN is just a simple text file containing technical info on how the ASP engines connects to the database.
As the directory is protected, what you could do is put the database file (mdb) into that directory, then reference it like this in the connection string:
<%
set conn = server.CreateObject("ADODB
connStr = "Driver={Microsoft Access Driver (*.mdb)};DBQ=" & Server.MapPath("--reviewdb
conn.open connStr
set qry = "SELECT * FROM usuarios"
set oRS = conn.Execute(qry)
if not oRS.EOF then
while not oRS.EOF
response.write ucase(fieldname) & ": " & oRs.Fields(fieldname) & "<br/> " ' <-- CHASE FIELDNAME TO BE A DATABASE TABLE FIELD i.e USER NAME
oRS.movenext
wend
oRS.close
end if
Set oRs = nothing
Set conn = nothing
%>