Question How to protect the FrontEnd

[genesis]

So I have opened the backend in my frontend by supplying the database password of the backend, so therefore, the backend is open in frontend.

Suppose I have another database and linked it to the frontend, will it connect there and see the data recorded? If so, how can I protect the FrontEnd?

T.Y.

 

[niak32]

Wow, looks like we are doing the same thing but i am one step behind you.

Would you mind showing in my thread how you got your front end to enter the password into the back end please?

http://www.access-programmers.co.uk/forums/showthread.php?p=876610#post876610

or link to the thread where it was solved if you don't mind.

Sorry to kind of hijack your thread

 

[Banana]

If you are still using .mdb and thus using ULS, you can deny the default user "Admin" the permissions to all tables & creating new table on the front-end, forcing the access to go through RWOP queries.

This will be adequate for preventing editing the tables outside of your design, but be aware of the following:

1) This is primarily useful as a corraling system rather than an actual security measure.
2) It does not necessarily prevent data from being imported out of the front-end.

 

[genesis]

thanks for the quick reply.

I have considered ULS. do you have other suggestions?

How about if I am using version 2007?

 

[Atomic Shrimp]

Although someone might be able to open the front end and export the data out of the linked tables from inside it, what they certainly won't be able to do is create a new empty database and import the tables from the front end

In order to link or import tables into database B from database A, they must actually reside in A, not be linked in there from somewhere else.

 

[Banana]

I can't make suggestions because a lot would depend on your specific needs, what you are trying to accomplish, and protect from what.

2007 nominally supports .mdb and thus ULS, but for any new file format (accdb), ULS is obsolete though the database password has been beefed up and it seems that it can be customized somewhat. It still is merely putting a heavier padlock on the screen door, though. Hence my references to corraling system rather than security.

Atomic Shrimp is quite correct on both points. (I was thinking of local tables in front-end but should have had qualified that earlier)

 

[genesis]

I have not tried it yet. I am going to use 2007. I am going to just secure the BE (database A) with database password and encrypt it. So with my FE (database B), I am going to link it, but I am afraid that with the FE, they can open the link tables there using other database (database C).

Without considering other security measures, how am I going to secure the FE (database B)?

Should I put database password there also and encrypt it? So if I am going to put db password there and encrypt it, everytime the FE will open, the password dialog box will appear, so How am I going to open the FE without the password dialog box to open?

Please assist me. Badly needed. thanks.

 

[Banana]

Did you read Atomic Shrimp's post and actually test it yourself? You would have had found that linked table weren't available for re-linked. You still have to connect to the database with the actual table to link to them, not via another database linking the same table.

 

[genesis]

No. I have not yet tested it myself yet. I was busy reading books and other references. So there is NO WAY for them to open the tables from the FE !

please confirm....thanks.

I would add something more.

For example, the FE (database B) also have its own table (not linked). So since this is not a linked table, therefore, database C can link to this tables in FE. But I still dont want those table to be seen due to its records inside those tables. Can I set the database password and encrypt it now? How can I set the database password in FE without having the password dialog box prompt everytime it is opened?