Secure Database Without Securing Data Access Page

[Guest]

I have an interesting problem.

In order to use a data access page that I have created, I need to store the
database in a public place on the network.

I want to protect the database from casual inspection from other users with
access to the public share, but do not want to have the data access page
protected by password.

I've tried a database password and workgroup security, but both impose a
password on the data access page.

Any suggestions?

 

[scott]

I have an interesting problem.

In order to use a data access page that I have created, I need to store the
database in a public place on the network.

I want to protect the database from casual inspection from other users with
access to the public share, but do not want to have the data access page
protected by password.

I've tried a database password and workgroup security, but both impose a
password on the data access page.

Any suggestions?

When you say "impose a password on the Data Access page", do you mean
that users must enter a password before they can view data? Assuming
you're using an Access db as your backend, this would be expected
behavior - your DAP pulls data from the datafile, therefore it would
require your users to enter a password before it could do so.

I'm not all that up on DAP, but from my understanding they're little
more than HTML pages with some Access specific stuff thrown in.
Perhaps you could examine the acutal scripts used to build the page
and find out exactly where the connection is being made, then alter
that script to provide the password through the script. Of course,
this would be easily ferretted out by a casual user, but at least
you'd keep honest people honest.