MS Access 2007 Password Protection

I have a framework 3.5 (Visual Studio 2008) solution that connect to an MS Access database. The database is password protected. In the IDE i am able to successfully connect and everything is fine. When i upload the site to your servers, i get the attached message. here is my connection string:
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<configSections>
</configSections>
<connectionStrings>
<add name="DAL.Properties.Settings.BlaBlaBla"
connectionString="Provider=Microsoft.ACE.OLEDB.12.0;Data Source=|DataDirectory|\BlaBlaBlaBla.accdb;Persist Security Info=True;Jet OLEDBatabase Password=blabla;"
providerName="System.Data.OleDb" />
</connectionStrings>
</configuration>

Im having a hard time trying to figure out why this is happening. Ive not seen any examples of a connection string using both the data directory and jet password. Any suggestions?

 

obviously - the attached message is not available - so it says:

not a valid password
blablabla

sry.

 

search is my friend

apparently the answer is:
"there is no answer."
consider this problem solved.

 

I believe Bruce tested this in the past and stated the password feature for Access DBes do not work on-line.
The only option will be to place the newer Access DBes in a protected folder.
I've been trying to get more info on this but Microsoft is only posting developer articles about the newer Access DBes with Cloud servers. Yup, you can actually buy protected Cloud hosting for that now, go figure. ;-)
All the best,
Mark

 

I appreciate the response. I wondered why no one had ever encountered this issue through googling. Now I get it.

 

oh i agree

as a matter of cost control though - if one were able to basically negate the need for an exotic data store via a web deployable password protected access database - i mean - thats pretty cheap in terms of licensing - and very effective. I use a lot of dataset objects (automatic plumbing) instead of writing stored procedures manually. The initial plan was to deliver a product with as little overhead as possible.

 

I feel your pain man, honest.
If you place the Access DB in your DASP provided _database folder it is protected form D/L, and if you are using ASP.NET your App_Data folder is as well.
Is that what you needed the PW protection for?
All the best,
Mark

 

yeah

a certain federal agency that i intend to do some data submission with, really likes buzzphrases - so i invented one. 3-layer security. Application layer (controled through web app) - Directory layer (for secure docs) - and database layer security. You get this inherently (if you are good lil boy design wise) - through SQL security. Not so much with access. I said "even if someone got a physical copy of the database somehow - they still couldnt access it if they didnt have the password." Now I look like a dumi. At least SQL is a pretty darn reasonable option in terms of what you guys provide.