|
|
|
|
|
| | |
| |
Active Server Pages ASP a directory of ASP tutorials applications scripts components and articles for the novice to professional developer. CJWSoft ASPProtect ASPBanner ASPClassifieds
(Advanced)
(Components)
(Database)
(General)
(Vbscript)
|
|
|
|
Subject: |
Re: SYSTEM DSN and ASP |
|
From: |
Chris Williams |
|
Date: |
2/22/1999 9:18:38 AM |
|
IP: |
205.219.18.178 |
For a system DSN do something like this
DataConn.Open "DSN=System_DSN_Name"
For a DSN-LESS conncetion do something like this
DataConn.Open "DBQ=" & Server.Mappath("_database/zipcodes.mdb") & ";Driver={Microsoft Access Driver (*.mdb)};"
Also.. system DSN'S do not offer as big a security advantage as you think. Whether you use a file/system or dsn-less connection people are not going to know where your database is no matter which of the 3 you use. If they dont know where it is they can't download it.
The best thing to do is password protect the access database and encript it.
Then if someone ever does download it they wont be able to open it without the password and if they view the source with a text editor it will all be scrambled. I never heard of any cracking utilities to unpassword protect access so its a good idea to do this and is relatively easy. I do it on all my storefronts at work if they use Access.
If the database is within the web site you should store it in an "_" directory like "_database". This adds protection against spiders which tend to find things you dont want them to.
Thats all I can think of. |
Previous Message
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
