An ASP for Access database security policy

This practice is more professional but also very safe and is now more popular practice, but now a lot of people just do half, just change the data name to ASP, so that directly with the FlashGet such as download tools can download the database, this way the correct approach is two steps:

Step One: Create a field in the database with the name random, the type is an OLE object, and the content is set to Single-byte "<%", that is (ASP code ChrB (ASC ("<") & ChrB ("%") run results)

Step Two: Rename the database to ASP

This will prompt a "missing shutdown script separator" If the database is requested directly from the URL. Thus refusing to download, because this way more trouble I found a small piece of code online to complete the OLE object insertion, as long as the database name set up, and then placed in the database and a directory to run it.

　

The full code reads as follows:

<%

Db= "D.mdb" is changed to your database address

Set Conn=server.createobject ("Adodb.connection")

Connstr= "Provider=Microsoft.Jet.OLEDB.4.0;Data source=" &server.mappath (db)

Conn.Open ConnStr

Conn.execute ("CREATE Table Notdownload (Notdown oleobject)")

Set Rs=server.createobject ("Adodb.recordset")

Sql= "SELECT * from Notdownload"

Rs.Open sql,conn,1,3

Rs.addnew

RS ("Notdown"). AppendChunk (ChrB (ASC ("<")) & ChrB (ASC ("%"))

Rs.update

Rs.close

Set rs=nothing

Conn.close

Set conn=nothing

%>

After this code is run, a nodownload table is generated in the database, and the field in the table is Notdown. If a data table with the same name already exists in the database, change the nodownload within the code to the name of the datasheet you want.