access front end

[RO|_F]

Hello,

Does anybody know if there are programs which do the following:
Act as 'front end' of a database (preferrably MS Access)
Encrypts or converts the contents of the database so that data is only
readable through the program?

Thanks,

Rolf
Utrecht, Netherlands

[WindAndWaves]

Hoi Rolf

ja dat kan....

If you run Access Runtime or set it in such a way that access runtime rather
than access opens the database then you can not read the tables as such and
you will have to use the front-end to access it.

However, this is by no means security. My question is - why do you want to
know, for security or other reasons???

"RO|_F" <20************@spamgourmet.com> wrote in message
news:40*********************@reader2.nntp.hccnet.n l...

Hello,

Does anybody know if there are programs which do the following:
Act as 'front end' of a database (preferrably MS Access)
Encrypts or converts the contents of the database so that data is only
readable through the program?

Thanks,

Rolf
Utrecht, Netherlands

---
Please immediately let us know (by phone or return email) if (a) this email
contains a virus
(b) you are not the intended recipient
(c) you consider this email to be spam.
We have done our utmost to make sure that
none of the above are applicable. THANK YOU
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.688 / Virus Database: 449 - Release Date: 18/05/2004

[RO|_F]

Hi,

bedankt voor je berichtje...

It is for security, our salesreps (or competitors) may not be able to copy
or alter the database which will be stored on each persons laptop.

regards,

Rolf

[Larry Linson]

This will not keep someone from using a disk read program to view the text
data. You can add encrypting code to encrypt before writing, and decrypt on
reading, but it will be your code. The encrypting Access does will prevent
someone poking around with a disk read program from seeing your text, but
anyone with Access (and necessary permissions, which your salesreps will
have to have if they are to use the database) can read an Access-encrypted
database).

I haven't seen a third-party product that automates this, but there are a
lot of third-party products around, and I don't even try to know about all
of them!

There is no way to keep someone from copying the whole database, as you will
be putting it in their hands. And, distributing with the runtime does not
keep someone with full retail Access from making a copy of the database to
use with Access. Even if you apply Access' security, it is relatively
easy/cheap to break.

For real _data security_, put the data on a server, and create a client
application to access it. While server databases aren't necessarily
foolproof (because, as they say, fools are so ingenious) they are much more
so than an Access/Jet database that you hand to someone. But that doesn't
work for beans if you need your users to carry the DB about with them on
notebook/laptop computers.

Alternative: do a good background check on those users to raise your
confidence that you can trust them.

Larry Linson
Microsoft Access MVP

"RO|_F" <10************@spamgourmet.com> wrote in message
news:40*********************@reader2.nntp.hccnet.n l...

Hi,

bedankt voor je berichtje...

It is for security, our salesreps (or competitors) may not be able to copy
or alter the database which will be stored on each persons laptop.

regards,

Rolf

[Bradley]

To make things a little more difficult... do the following to your
back-end:
- rename it from .mdb to something else (and modify your relink code)
- add an Autoexec or startup form that will either shut the application
immediately or display a message first (if they try to open it directly
in Access)
- I think you can add a database password (but can't remember how this
effects linking?)

I reckon if MS recommends setting up a networked database as front/back
end then they should perhaps offer a .MDE-ish type "data only" file to
use for the backend.. one that only allows linking to by authorised
users and no direct access (if you choose)...... for all those with out
the resources to go to MSSQL/etc.
--
regards,

Bradley
Larry Linson wrote:

This will not keep someone from using a disk read program to view the
text data. You can add encrypting code to encrypt before writing, and
decrypt on reading, but it will be your code. The encrypting Access
does will prevent someone poking around with a disk read program from
seeing your text, but anyone with Access (and necessary permissions,
which your salesreps will have to have if they are to use the
database) can read an Access-encrypted database).

I haven't seen a third-party product that automates this, but there
are a lot of third-party products around, and I don't even try to
know about all of them!

There is no way to keep someone from copying the whole database, as
you will be putting it in their hands. And, distributing with the
runtime does not keep someone with full retail Access from making a
copy of the database to use with Access. Even if you apply Access'
security, it is relatively easy/cheap to break.

For real _data security_, put the data on a server, and create a
client application to access it. While server databases aren't
necessarily foolproof (because, as they say, fools are so ingenious)
they are much more so than an Access/Jet database that you hand to
someone. But that doesn't work for beans if you need your users to
carry the DB about with them on notebook/laptop computers.

Alternative: do a good background check on those users to raise your
confidence that you can trust them.

Larry Linson
Microsoft Access MVP

"RO|_F" <10************@spamgourmet.com> wrote in message
news:40*********************@reader2.nntp.hccnet.n l...

Hi,

bedankt voor je berichtje...

It is for security, our salesreps (or competitors) may not be able
to copy or alter the database which will be stored on each persons
laptop.

regards,

Rolf

--
regards,

Bradley

[RO|_F]

Alternative: do a good background check on those users to raise your
confidence that you can trust them.

Larry Linson
Microsoft Access MVP

Thanks for your answer. It seems to be not that easy as I thought or
expected.
Storing the database on a server is no option since people are on the
'field' . Then they would need a (expensive) dial in solution to consult the
database every time they visit a customer.

Regards,

Rolf