How to prevent savy users from linking to BE tables?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I have split a db to where each user has their own copy of the FE stored on
their machine-thanks to Tony's Auto FE Updater utility. Their .ini
file/shortcut points to a network location in the Survey db's sub-folder FE
(ServerName\Survey db folder\FE sub-folder\) that all users have access to
and obtains a copy of the master FE .mdb if the version is different. The
back-end database is stored in that same location in the BE sub-folder
(ServerName\Survey db folder\BE sub-folder\).

The FE has the shift-key and F11 database window key disabled. All toolbar
menus that allow a user to change forms have been disabled. As far as I can
tell, no user can get access to the data in the tables unless they have or
create an .mdb that can re-enable the database window or shiftkey or menu
bars. I will assume most users do not know how to do that.

However, I do know that some of my users know how to create linked tables in
an Access database. This concerns me b/c that means that if they know where
the data is stored (back-end tables), they can create an .mdb that has linked
tables to the back-end tables. As I said above, the back-end .mdb is merely
in a sub-folder that the master front-end is stored in that users
..ini/shortcut points to when looking to see if there is a more recent FE
version.

I can move the BE to a completely different folder, but it still has to be a
folder that the users have full rights to, otherwise they won't be able to
ultimately write data to the back-end tables, etc. But they can open
"Windows Explorer" or "My Computer" and scroll the server to find where I put
it by looking at folder names to find one that relates to the name of the
database. Would "hiding" it prevent the user from seeing the folder on the
server if they scroll randomly around in "My Computer"?

Thanks for your help!
Heather
.

Relevant Pages

  • Re: Un-Split
    ... the Front-End and the Back-End? ... Back-End on a drive C folder, where you will instruct him to install in the ... backup files in the same folder would do! ... database back into one big file so I can send that to him? ...
    (microsoft.public.access.setupconfig)
  • Re: Bloody obvious question
    ... This is because Access creates a locking file in that folder when the first user accesses the database, updates it as subsequent users access the database, and deletes it when the last user closes the database. ... BTW, make sure you split the database into a front-end, linked to a back-end. ... Only the back-end should be on the server: each user should have his/her own copy of the front-end, ...
    (microsoft.public.access.gettingstarted)
  • Re: Timer To Shut down database when idle
    ... the folder where the back-end database exists, ... >>> network drives. ...
    (microsoft.public.access.formscoding)
  • Re: Bloody obvious question
    ... the folder where the MDB file exists, ... database, and deletes it when the last user closes the database. ... Only the back-end should be on the server: ... coming from MySQL and more server orientated databases. ...
    (microsoft.public.access.gettingstarted)
  • Re: Is there blog add on for FP2003
    ... tools/ web settings/ database tab. ... browse to the .mdb for the blog and add it. ... you'll have to edit the config file to reflect the new folder name. ... >>Microsoft MVP FrontPage ...
    (microsoft.public.frontpage.addins)