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

Question about importing objects

P: n/a
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
Nov 13 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
"ANSWER" wrote in message:
news:d4**********@ariane.blic.net...
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.


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
in the M.P.A newsgroups. 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/JCR....html#Security>>>>>>>


--
Jeff Conrad
Access Junkie
Bend, Oregon

----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----
Nov 13 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.