How can I force users to use only the front-end of a database? 
Author Message
 How can I force users to use only the front-end of a database?

I have a database with a front-end and a back-end. Some users go directly to
the back-end tables to enter data bypassing any  record keeping that I do in
the front-end. Most of the 'offenders' are software people and can figure
out most simple work-arounds that I have come up  with (like changing the
.mdb extension to .dll).

How can I force users to use only the front-end of a database?

ed



Sat, 31 Jul 2004 01:44:43 GMT  
 How can I force users to use only the front-end of a database?
I put a database password on the back-end and 'linked' the back-end table to
the front-end. I had to use the password once to link the back-end table,
but did not need to use it again on normal front-end use of that 'protected'
table.

Does anyone see a problem with this approach?

ed

Quote:
> I have a database with a front-end and a back-end. Some users go directly
to
> the back-end tables to enter data bypassing any  record keeping that I do
in
> the front-end. Most of the 'offenders' are software people and can figure
> out most simple work-arounds that I have come up  with (like changing the
> .mdb extension to .dll).

> How can I force users to use only the front-end of a database?

> ed



Sat, 31 Jul 2004 05:11:11 GMT  
 How can I force users to use only the front-end of a database?


Quote:
>I have a database with a front-end and a back-end. Some users go directly to
>the back-end tables to enter data bypassing any  record keeping that I do in
>the front-end. Most of the 'offenders' are software people and can figure
>out most simple work-arounds that I have come up  with (like changing the
>.mdb extension to .dll).

>How can I force users to use only the front-end of a database?

Implement database security, and don't give any of them an
administrator password. Or persuade their supervisor that this is
unethical behavior and grounds for disciplinary action... Even these
will be breakable if they are sufficiently determined. It's not going
to be trivial.

Do they understand why the recordkeeping is a business necessity? If
so they're just being VERY rude!

                  John W. Vinson[MVP]    
    Come for live chats every Tuesday and Thursday
http://go.compuserve.com/msdevapps?loc=us&access=public



Sat, 31 Jul 2004 05:44:27 GMT  
 How can I force users to use only the front-end of a database?


Quote:
>I put a database password on the back-end and 'linked' the back-end table to
>the front-end. I had to use the password once to link the back-end table,
>but did not need to use it again on normal front-end use of that 'protected'
>table.

>Does anyone see a problem with this approach?

Other than the fact that there are at least a halfdozen easy to find
websites describing how to break password security, no.  Locks like
this only keep out honest people. <g>

Actually full Access security can be cracked too; it will lock out
dishonest people too if they're not very clever.

                  John W. Vinson[MVP]    
    Come for live chats every Tuesday and Thursday
http://go.compuserve.com/msdevapps?loc=us&access=public



Sat, 31 Jul 2004 08:36:53 GMT  
 
 [ 4 post ] 

 Relevant Pages 

1. Access database corruption using vb front ends

2. Using Visual Basic to front-end an Oracle Database

3. Help - using VB as front end for Access Database

4. ASP User wants to create VB Front-end for Access DB

5. Trying to backup a database from front end w/ FileCopy

6. Corruption of Database Front End

7. Database Front End Sample

8. Database Front End

9. Visual Basic Front Ends For Access Databases

10. Database Front End

11. Connecting Sun database to Visual Basic front end

12. Connect Sun database to VB front end

 

 
Powered by phpBB® Forum Software