About importing objects

  • Thread starter Thread starter Rick B
  • Start date Start date
Instead of giving users access to the tables, you might set up RWOP (read
with owner permissions) queries. The RWOP queries could omit columns from
the tables, or only provide a subset of the data. Users would still be able
to get data from the queries, but it may not be as useful as the entire
table.
 
ANSWER said:
I post similar questions sometimes before but I have never get right
answer.
Please help me it is very delicate.

Is there any way I could disable user to create a new database and import
all of my tables and queries into his database.
I make .mde, disable shift+Enter, make logon users module (with your help
sometimes before) but still my tables and queries are free to take.
If you know couple solutions please let me know so I can decide.

Thanks
Click to expand...
You need to hide the database window from your users, disable the start-up
bypass (shift) key and invoke user-level security (ULS). ULS requires a
significant amount of time and patience to master. See the relevant links
on my website for more information and be sure to work on *copies* of your
files in case you lock yourself out. If you implement ULS correctly then
casual users will not be able to import any of your objects, including
tables.

Regards,
Keith.
www.keithwilby.com
 
I post similar questions sometimes before but I have never get right answer.
Please help me it is very delicate.

Is there any way I could disable user to create a new database and import
all of my tables and queries into his database.
I make .mde, disable shift+Enter, make logon users module (with your help
sometimes before) but still my tables and queries are free to take.
If you know couple solutions please let me know so I can decide.

Thanks
 
in message:
I post similar questions sometimes before but I have never get right answer.
Please help me it is very delicate.

Is there any way I could disable user to create a new database and import
all of my tables and queries into his database.
I make .mde, disable shift+Enter, make logon users module (with your help
sometimes before) but still my tables and queries are free to take.
If you know couple solutions please let me know so I can decide.
Click to expand...

Humm...are you the same person I responded to twice already? I replied
to your question both times; once on Feb 25th and once on March 2nd.
You never replied back with any additional questions and/or problems.

The end result you want to achieve is "do-able" it will just take quite a bit
of your time to set everything up. There is no "quick and easy" way to do
this. It can be a long process based on the complexity of your application.
If you need our help, you will have to give specifics as to what you have
done so far and what exactly you need help with.

Here is a copy of my reply to your question on March 2nd:I already answered your question in the general Access forum newsgroup
two hours after you posted the message on Feb 25.
Did you not see my reply?

Here it is again:

The only way to do this is to implement full blown Access User Level
Security (ULS). You would then deny all permissions on the tables
themselves and create RWOP queries for the users to access the table
information. Assigning appropriate permissions to various database objects
would also be needed. The users could still possibly import the queries
into another container, but they would essentially be worthless since
they would not be able to access the data in the BE file. You could
also distribute MDE files (a good idea anyway) which would prevent
tampering with your code and prevent importing of forms, macros,
reports, and modules.

If you have never used ULS before, be prepared for a lot of work ahead
of you. ULS is not a trivial undertaking at all so I would recommend
ALL of the following reading material before beginning. Also, practice
on dummy databases until you are really comfortable with it.

http://www.ltcomputerdesigns.com/JCReferences.html#Security
 
Back
Top