Lets say I apply "password" to northwind.mdb. When I run MSAccess, I enter
"password" at the prompt and I am in.

Now another person starts a second instance of MSAccess. Since
Northwind.mdb is already opened in one instance of Access, they can connect
to northwind.mdb from the second instance without having to know or enter
the password!

Is there any way of preventing this?

Thanks.

Neil,

Not sure how you set up the security but that shouldn't happen. Have a look
at...

http://www.jmwild.com/

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

"Neil W" <(E-Mail Removed)> wrote in message
news:#(E-Mail Removed)...
Lets say I apply "password" to northwind.mdb. When I run MSAccess, I enter
"password" at the prompt and I am in.

Now another person starts a second instance of MSAccess. Since
Northwind.mdb is already opened in one instance of Access, they can connect
to northwind.mdb from the second instance without having to know or enter
the password!

Is there any way of preventing this?

Thanks.

Thanks for the reply, but can you be more specific? Is there a specific
article or tip I should look at?


"Gina Whipp" <(E-Mail Removed)> wrote in message
news:B8BE09F7-8E41-4BA9-9D9B-(E-Mail Removed)...
> Neil,
>
> Not sure how you set up the security but that shouldn't happen. Have a
> look
> at...
>
> http://www.jmwild.com/
>
> --
> Gina Whipp
> 2010 Microsoft MVP (Access)
>
> "I feel I have been denied critical, need to know, information!" - Tremors
> II
>
> http://www.regina-whipp.com/index_files/TipList.htm
>
> "Neil W" <(E-Mail Removed)> wrote in message
> news:#(E-Mail Removed)...
> Lets say I apply "password" to northwind.mdb. When I run MSAccess, I
> enter
> "password" at the prompt and I am in.
>
> Now another person starts a second instance of MSAccess. Since
> Northwind.mdb is already opened in one instance of Access, they can
> connect
> to northwind.mdb from the second instance without having to know or enter
> the password!
>
> Is there any way of preventing this?
>
> Thanks.
>

Neil,

Try starting here...

http://www.ltcomputerdesigns.com/Security.htm

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

"Neil W" <(E-Mail Removed)> wrote in message
news:eR#(E-Mail Removed)...
Thanks for the reply, but can you be more specific? Is there a specific
article or tip I should look at?


"Gina Whipp" <(E-Mail Removed)> wrote in message
news:B8BE09F7-8E41-4BA9-9D9B-(E-Mail Removed)...
> Neil,
>
> Not sure how you set up the security but that shouldn't happen. Have a
> look
> at...
>
> http://www.jmwild.com/
>
> --
> Gina Whipp
> 2010 Microsoft MVP (Access)
>
> "I feel I have been denied critical, need to know, information!" - Tremors
> II
>
> http://www.regina-whipp.com/index_files/TipList.htm
>
> "Neil W" <(E-Mail Removed)> wrote in message
> news:#(E-Mail Removed)...
> Lets say I apply "password" to northwind.mdb. When I run MSAccess, I
> enter
> "password" at the prompt and I am in.
>
> Now another person starts a second instance of MSAccess. Since
> Northwind.mdb is already opened in one instance of Access, they can
> connect
> to northwind.mdb from the second instance without having to know or enter
> the password!
>
> Is there any way of preventing this?
>
> Thanks.
>

Neil, there's no way that it can be diagnosed over the Internet. Try reading
these articles and following them exactly:

Security FAQ
http://support.microsoft.com/support...ent/secfaq.asp

Lynn Trapp's summarization:
http://www.ltcomputerdesigns.com/The10Steps.htm

KB articles:
http://support.microsoft.com/default...;en-us;q165009
http://download.microsoft.com/downlo...-us/secfaq.exe
http://support.microsoft.com/default.aspx?kbid=325261

Joan Wild's articles:
http://www.jmwild.com/security02.htm
http://www.jmwild.com/security97.htm
http://www.jmwild.com/SecureNoLogin.htm
http://www.jmwild.com/Unsecure.htm
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.accessmvp.com
http://www.mvps.org/access


"Neil W" <(E-Mail Removed)> wrote in message
news:eR%(E-Mail Removed)...
> Thanks for the reply, but can you be more specific? Is there a specific
> article or tip I should look at?
>
>
> "Gina Whipp" <(E-Mail Removed)> wrote in message
> news:B8BE09F7-8E41-4BA9-9D9B-(E-Mail Removed)...
>> Neil,
>>
>> Not sure how you set up the security but that shouldn't happen. Have a
>> look
>> at...
>>
>> http://www.jmwild.com/
>>
>> --
>> Gina Whipp
>> 2010 Microsoft MVP (Access)
>>
>> "I feel I have been denied critical, need to know, information!" -
>> Tremors
>> II
>>
>> http://www.regina-whipp.com/index_files/TipList.htm
>>
>> "Neil W" <(E-Mail Removed)> wrote in message
>> news:#(E-Mail Removed)...
>> Lets say I apply "password" to northwind.mdb. When I run MSAccess, I
>> enter
>> "password" at the prompt and I am in.
>>
>> Now another person starts a second instance of MSAccess. Since
>> Northwind.mdb is already opened in one instance of Access, they can
>> connect
>> to northwind.mdb from the second instance without having to know or enter
>> the password!
>>
>> Is there any way of preventing this?
>>
>> Thanks.
>>
>
>

Stewart Berman wrote:

> I did not see any information on how to secure an Access 2007 accdb or
> accde database.
>
> Microsoft has chosen to remove workgroup security for accdb and accde
> files. So you now have to roll your own.
>
> Do you have any information on securing the current MS Access database
> structure? In particular how do you secure the database against an
> authorized user -- someone with read/write access to the folder the
> database is in and who has the password -- from poking around in it?

You can't. If you want security that applies to people allowed to open your
file then revert to MDB format or use a server database like SQL Server.

I did not see any information on how to secure an Access 2007 accdb or accde
database.

Microsoft has chosen to remove workgroup security for accdb and accde files.
So you now have to roll your own.

Do you have any information on securing the current MS Access database
structure? In particular how do you secure the database against an
authorized user -- someone with read/write access to the folder the database
is in and who has the password -- from poking around in it?

"Arvin Meyer [MVP]" <(E-Mail Removed)> wrote:

>Neil, there's no way that it can be diagnosed over the Internet. Try reading
>these articles and following them exactly:
>
>Security FAQ
>http://support.microsoft.com/support...ent/secfaq.asp
>
>Lynn Trapp's summarization:
>http://www.ltcomputerdesigns.com/The10Steps.htm
>
>KB articles:
>http://support.microsoft.com/default...;en-us;q165009
>http://download.microsoft.com/downlo...-us/secfaq.exe
>http://support.microsoft.com/default.aspx?kbid=325261
>
>Joan Wild's articles:
>http://www.jmwild.com/security02.htm
>http://www.jmwild.com/security97.htm
>http://www.jmwild.com/SecureNoLogin.htm
>http://www.jmwild.com/Unsecure.htm

Thanks. Can RevokeActiveObject be used to stop another program from doing a
GetObject on that Access database?

"Rick Brandt" <(E-Mail Removed)> wrote in message
news:hrd3eh$qsk$(E-Mail Removed)...
> Stewart Berman wrote:
>
>> I did not see any information on how to secure an Access 2007 accdb or
>> accde database.
>>
>> Microsoft has chosen to remove workgroup security for accdb and accde
>> files. So you now have to roll your own.
>>
>> Do you have any information on securing the current MS Access database
>> structure? In particular how do you secure the database against an
>> authorized user -- someone with read/write access to the folder the
>> database is in and who has the password -- from poking around in it?
>
> You can't. If you want security that applies to people allowed to open
> your
> file then revert to MDB format or use a server database like SQL Server.

You can build an ACCDE, which keeps them from idly poking around the
objects, but not the data.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.accessmvp.com
http://www.mvps.org/access


"Stewart Berman" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I did not see any information on how to secure an Access 2007 accdb or
>accde
> database.
>
> Microsoft has chosen to remove workgroup security for accdb and accde
> files.
> So you now have to roll your own.
>
> Do you have any information on securing the current MS Access database
> structure? In particular how do you secure the database against an
> authorized user -- someone with read/write access to the folder the
> database
> is in and who has the password -- from poking around in it?
>
> "Arvin Meyer [MVP]" <(E-Mail Removed)> wrote:
>
>>Neil, there's no way that it can be diagnosed over the Internet. Try
>>reading
>>these articles and following them exactly:
>>
>>Security FAQ
>>http://support.microsoft.com/support...ent/secfaq.asp
>>
>>Lynn Trapp's summarization:
>>http://www.ltcomputerdesigns.com/The10Steps.htm
>>
>>KB articles:
>>http://support.microsoft.com/default...;en-us;q165009
>>http://download.microsoft.com/downlo...-us/secfaq.exe
>>http://support.microsoft.com/default.aspx?kbid=325261
>>
>>Joan Wild's articles:
>>http://www.jmwild.com/security02.htm
>>http://www.jmwild.com/security97.htm
>>http://www.jmwild.com/SecureNoLogin.htm
>>http://www.jmwild.com/Unsecure.htm

"Arvin Meyer [MVP]" <(E-Mail Removed)> wrote:

>You can build an ACCDE, which keeps them from idly poking around the
>objects, but not the data.

Accde only protects code. All of the other objects are unprotected.