Re: preventing user to access/see/import/linking tables

On Feb 13, 12:01 am, Tom van Stiphout <no.spam.tom7...@xxxxxxx> wrote:
On Tue, 12 Feb 2008 20:29:27 -0800, "Fred Zuckerman"

<Zuckerm...@xxxxxxxxxxxxx> wrote:

Yes. You can still run it, but not create it.

I am writing code to check with Active Directory as to who is a member
of what group.

Define "it".

-Tom.

"Tom van Stiphout" <no.spam.tom7...@xxxxxxx> wrote in message
news:fjr4r3dcr5a1nesmifpghflmqeq0muuq52@xxxxxxxxxx
On Tue, 12 Feb 2008 03:13:10 -0800 (PST), thread <yaniv...@xxxxxxxxx>
wrote:

The most secure, albeit not perfectly secure, way is to use Workgroup
Security. Phased out in A2007, so that should tell you something.
If you want real security, SQL Server can provide it, including the
free Express edition.

-Tom.

.mdw is phased out in A2007???
Is there an alternative?
Is it backwards compatible with A2k?
tks,
Fred Zuckerman

I'm not very security-ish but when I run this

Debug.Print CurrentProject.BaseConnectionString

in the new downloadable or sample Northwind 2007.accdb

I get this:

PROVIDER=Microsoft.ACE.OLEDB.12.0;DATA SOURCE=C:\Users\lyle fairfield
\Documents\Access\Northwind 2007.accdb;PERSIST SECURITY INFO=FALSE;Jet
OLEDB:System database=C:\Users\lyle fairfield\AppData\Roaming\Microsoft
\Access\System.mdw

Is this related to your statement you can run it but not create it?
How please?

.