Security and My Backend

[dynamictiger]

I have had a coupla goes at security, but seem to be getting it wrong, so I thought I would ask you guys for some help here.

I have an application with a front end and a back end.

The front end is sufficently secure as an MDE file. However I am concerned about the backend. So far I have set up a password form to show the tables in a list box then click through to design view, which I think is a good move. However, this does not stop someone with a copy of XP importing my tables. I know the security wizard can do this, but so far it seems everytime I try and secure my backend I cause an error for reading data from my frontend.

If someone has a few minutes to spare considering this. I do not need heavy security. I am only trying to stop my table structure being robbed, nothing less, nothing more.

 

[KenReay]

Hi

I have not found anything which is totally secure, but if you are just trying to keep prying users out, these ideas might help:

Make your backend a hidden file, so it does not appear in the directory listing.

Put it on a hidden Network Share

Hide the Database Window

I have actually gone beyond thsi to use code to disable the bypass key etc, but it depends how sophisticated your 'soies' are as to how far you need to go

Regards

Ken Reay

 

[Francescina]

Here is the complete solution for your problem, I found it in the ACCESS ONLINE ENCYCLOPEDIA (

http://www.unsoftwareag.com).

It should work with both A2K and A2002

Article Code: S4

Security of the backend tables ?
PROBLEM


If you activate the security system on the frontend all database objects are securized.
In a split application all tables from the backend file are linked into the frontend file. It is not possible to link tables from a securized backend file even if you use the same MDW file for backend and frontend.


SOLUTION

You have three possibilities to solve this problem:
Integration with DAO (Opendatabase) (A97 and A2K)
Integration with ADOX (Setpermissions)(only A2K)
Utilization of queries with "OwnerAccess" option

The first two solutions require that you transmit both username and password, therefore the third solution is the most secure.


Creation of a query with "OwnerAccess"

Log in with write rights on the securized table
Create a new query
Activate the query property "OwnerAccess" in the query window
Save the query
This query can be used by all logged-in users.
If you use SQL strings in your VBA code then use the following structure:


SELECT Field1,Field2 FROM tableName WITH OWNERACCESS OPTION