By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,606 Members | 3,802 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,606 IT Pros & Developers. It's quick & easy.

Stop Importing of Tables without RWOP

P: n/a
I've done all the recommended things with workgroup security, creating a
..mde file, and splitting the application into a front end and, in my case,
multiple backends.

The problem is that users that have access to the application (thru the
custom workgroup file) can import the tables into a blank database.

My application has no queries and uses SQL statements in the VBA code to
read/update table information. I have hundreds of SQL statements so I don't
see creating queries with RWOP as a possibility (however, please correct me
if I'm wrong).

I am using database passwords on the backends, but am concerned about how
easy they apparantly are to crack. Still, this does deter users from
importing since no one has the backend passwords except me (as the
developer).

Is there anything else I can do, besides hiding the sensitive tables?

Thanks.

--
Message posted via http://www.accessmonster.com
Nov 13 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
I had the same trouble and went down the route of reporting them to senior
managers. They were not too concerned so the only way I found to get round
the problem was to take the privileges away from the users to open/read the
tables. All the queries were stored in the database and run with the owners
permission. (with owneraccess option). This way, not only do they need the
database password, they will need the workgroup Admin password. When they
try to import the tables, they will receive a message stating they do not
have the necessary privileges.

Mark
"robert demo via AccessMonster.com" <fo***@AccessMonster.com> wrote in
message news:df******************************@AccessMonste r.com...
I've done all the recommended things with workgroup security, creating a
..mde file, and splitting the application into a front end and, in my case,
multiple backends.

The problem is that users that have access to the application (thru the
custom workgroup file) can import the tables into a blank database.

My application has no queries and uses SQL statements in the VBA code to
read/update table information. I have hundreds of SQL statements so I don't
see creating queries with RWOP as a possibility (however, please correct me
if I'm wrong).

I am using database passwords on the backends, but am concerned about how
easy they apparantly are to crack. Still, this does deter users from
importing since no one has the backend passwords except me (as the
developer).

Is there anything else I can do, besides hiding the sensitive tables?

Thanks.

--
Message posted via http://www.accessmonster.com
Nov 13 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.