Blocking users from accessing Access database

[kai]

Hi, All
I try to block some one import my Access database tables using Access
database.

I used password protection, but if some one crack through my password, are
there any other methods to block some one importing my tables using Access
database?

Thanks

kai

[Larry Linson]

"kai" wrote

I used password protection, but if some
one crack through my password, are
there any other methods to block some
one importing my tables using Access
database?

No, not that I know of, if they break security (and it isn't all that
difficult). Security on a desktop database that someone can copy as a file,
take away, and work on at their leisure isn't ever going to be as good as
security on a server database. If your data tables are very important to
you, that would be the way to go -- a server database with an Access
front-end.

Larry Linson
Microsoft Access MVP

[kai]

Larry,
Thanks
Kai
"Larry Linson" <bo*****@localhost.not> wrote in message
news:khO4d.1375$Jj4.548@trnddc06...

"kai" wrote

I used password protection, but if some
one crack through my password, are
there any other methods to block some
one importing my tables using Access
database?

No, not that I know of, if they break security (and it isn't all that
difficult). Security on a desktop database that someone can copy as a
file,
take away, and work on at their leisure isn't ever going to be as good as
security on a server database. If your data tables are very important to
you, that would be the way to go -- a server database with an Access
front-end.

Larry Linson
Microsoft Access MVP

[kai]

Larry,
Is it possible when some try to import tables from current data, the
database pops a from (user defined form) to request username and password?

Thanks

kai
"Larry Linson" <bo*****@localhost.not> wrote in message
news:khO4d.1375$Jj4.548@trnddc06...

"kai" wrote

I used password protection, but if some
one crack through my password, are
there any other methods to block some
one importing my tables using Access
database?

No, not that I know of, if they break security (and it isn't all that
difficult). Security on a desktop database that someone can copy as a
file,
take away, and work on at their leisure isn't ever going to be as good as
security on a server database. If your data tables are very important to
you, that would be the way to go -- a server database with an Access
front-end.

Larry Linson
Microsoft Access MVP

[Larry Linson]

I am not aware of any mechanism by which you can be aware that someone is
importing from your database -- there's no event. In fact, you can import
objects from a database that isn't open (it may be, internally, temporarily
"opened"). You can apply Access security, but as I mentioned, that can be
broken.

My view of "user defined forms" for name/password security is that is, at
best, "security lite", even easier to defeat than Access' own builtin
security. I have, in the distant past, implemented a security lite scheme,
but only after I had been strong in my warnings to the client that it was,
essentially, worthless. They took the view that the people using it would be
unfamiliar with computers (computer-illiterate) and wouldn't even _try_ to
get around it. I am sure they were wrong; the only "saving grace" was that
version never went into production; the version that did go into production
had been converted to an Access client to an SQL Server database, so they
had the security of the server and of SQL Server.

Larry Linson
Microsoft Access
"kai" <ka******@earthlink.net> wrote in message
news:UA*****************@newsread3.news.pas.earthl ink.net...

Larry,
Is it possible when some try to import tables from current data, the
database pops a from (user defined form) to request username and password?

Thanks

kai
"Larry Linson" <bo*****@localhost.not> wrote in message
news:khO4d.1375$Jj4.548@trnddc06...

"kai" wrote

I used password protection, but if some
one crack through my password, are
there any other methods to block some
one importing my tables using Access
database?

No, not that I know of, if they break security (and it isn't all that
difficult). Security on a desktop database that someone can copy as a
file,
take away, and work on at their leisure isn't ever going to be as good as security on a server database. If your data tables are very important to
you, that would be the way to go -- a server database with an Access
front-end.

Larry Linson
Microsoft Access MVP

[kai]

Thank you very much Larry

Kai
"Larry Linson" <bo*****@localhost.not> wrote in message
news:qi15d.42$Ym1.31@trnddc03...

I am not aware of any mechanism by which you can be aware that someone is
importing from your database -- there's no event. In fact, you can import
objects from a database that isn't open (it may be, internally,
temporarily
"opened"). You can apply Access security, but as I mentioned, that can be
broken.

My view of "user defined forms" for name/password security is that is, at
best, "security lite", even easier to defeat than Access' own builtin
security. I have, in the distant past, implemented a security lite scheme,
but only after I had been strong in my warnings to the client that it was,
essentially, worthless. They took the view that the people using it would
be
unfamiliar with computers (computer-illiterate) and wouldn't even _try_ to
get around it. I am sure they were wrong; the only "saving grace" was that
version never went into production; the version that did go into
production
had been converted to an Access client to an SQL Server database, so they
had the security of the server and of SQL Server.

Larry Linson
Microsoft Access
"kai" <ka******@earthlink.net> wrote in message
news:UA*****************@newsread3.news.pas.earthl ink.net...

Larry,
Is it possible when some try to import tables from current data, the
database pops a from (user defined form) to request username and
password?

Thanks

kai
"Larry Linson" <bo*****@localhost.not> wrote in message
news:khO4d.1375$Jj4.548@trnddc06...

> "kai" wrote
>
> > I used password protection, but if some
> > one crack through my password, are
> > there any other methods to block some
> > one importing my tables using Access
> > database?
>
> No, not that I know of, if they break security (and it isn't all that
> difficult). Security on a desktop database that someone can copy as a
> file,
> take away, and work on at their leisure isn't ever going to be as good as > security on a server database. If your data tables are very important
> to
> you, that would be the way to go -- a server database with an Access
> front-end.
>
> Larry Linson
> Microsoft Access MVP
>
>