Wrox Programmer Forums
Go Back   Wrox Programmer Forums > Microsoft Office > Access and Access VBA > Access
|
Access Discussion of Microsoft Access database design and programming. See also the forums for Access ASP and Access VBA.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Access section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old December 12th, 2008, 10:28 AM
Registered User
 
Join Date: Dec 2008
Posts: 2
Thanks: 1
Thanked 0 Times in 0 Posts
Default Limit imports from my Access 2003 database

Suppose I have an MS Access 2003 database called X.mdb. If I create a blank MS Access 2003 database, I could use the Import Wizard to import information from X.mdb to the blank database.If I password protect the VB code in X.mdb and deny the user access to the startup dialog box, I can prevent the importation of VB code from X.mdb. To import a module, a person would first have to remove the password protection. Is there a way to block the importation of certain tables, queries, forms, reports, or macros?When I give my database to my customer, I don't want them to import certain tables or queries from my database.
 
Old December 12th, 2008, 02:52 PM
Friend of Wrox
 
Join Date: Mar 2004
Posts: 3,069
Thanks: 0
Thanked 10 Times in 10 Posts
Default

Testing to see if this post works. I don't like this new site.
__________________
mmcdonal

Look it up at: http://wrox.books24x7.com
 
Old December 12th, 2008, 02:55 PM
Friend of Wrox
 
Join Date: Mar 2004
Posts: 3,069
Thanks: 0
Thanked 10 Times in 10 Posts
Default

Okay, the Title text box is very distracting.

You can't limit tables in Access like this, nor I think in most other databases. You have to give the users some access to the data, and in so doing, they have a full range of activities they can do with the data, including exporting tables. This is why some developers either use obfuscated data, so even if they get it, they can't do anything with it, OR use a proprietary back end without providing an ODBC driver - unless a separate charge is paid.

If you really want to prevent your users from getting at their own data, you will want to use on of these other methods. I would bet lunch on that.
__________________
mmcdonal

Look it up at: http://wrox.books24x7.com
The Following User Says Thank You to mmcdonal For This Useful Post:
esharris (December 12th, 2008)





Similar Threads
Thread Thread Starter Forum Replies Last Post
Load access 2003 database in memory Koeno Pro VB Databases 2 September 21st, 2008 12:27 PM
Converting Access 97 database to 2003 RonK Access 3 June 7th, 2008 11:52 PM
Running 97 Access Database in 2003 etherz Access 9 May 14th, 2008 08:14 AM
URL Checker for a Microsoft Access 2003 Database Corey Access 17 December 8th, 2005 04:21 PM
Is there a limit to # of datafields in Access? rayncarnation ASP.NET 1.0 and 1.1 Basics 0 October 11th, 2005 09:05 AM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.