
Thank you for your responses.
I still didn't feel comfortable just having the database information there and visible in the code, so, I added an include file which has encryption and decryption modules I wrote, and encrypted the database access variables.
So, the information is still there, but a hacker will have to get access to the SQL connection asp, plus the include file (albeit that file name is included in the SQL connection asp), and then write some code to decipher the information.
For those who may be interested (and I apologize if this is the wrong forum for this aspect of this topic) the modified code now looks like this:
%><!--#include file="functions/functions_other.asp" --><%
'Enter the details of your SQL server below
strSQLServerName = Decrypt("rrarrerrskqskqskqerrqrkrrkarknrrnrrerkrrrqrkrrkkrrnrknrrerkrkqekssrrrrks")
strSQLDBUserName = Decrypt("rrmrrnrrqknkknkknqkqsknnkqlkqsknpkqs")
strSQLDBPassword = Decrypt("kenkemknaknpkql")
strSQLDBName = Decrypt("rrqrprrrprrkrrrrrqrka")