Question Split database

asif pasha

Registered User.
Local time
Today, 14:57
Joined
Jan 8, 2010
Messages
60
Hi,

I was wondering is there any way to protect the code or not to show the code in the database?

Also is there a way to protect the tables, because many of us here know how to link the table from different database, i was looking an option where we can't link the table?

Thanks in advance.

Regards,
Asif
 
You can password lock the modules.

You can password lock the backend database. You will have to relink your tables, the password will be stored within the linked tables when you are asked for the password to the tables in the backend and the user will never see it.

Access 2007 and newer does not use workgroup security which is a great way to lock down your Access 2003 and older database objects but it is tricky and you can lock yourself out of your database if you are not careful.
 
Could you please explain, how to do this.
 
Two parts. You have to password protect the backend database. That file as a whole can have a transparent password on it if your linked tables have a .Connect string that includes the password as well as the path to the database. Look up TableDef objects for the property .Connect, which will tell you how to include passwords for the Backend in the Frontend.

Then compile the .MDB Frontend file into an .MDE (be SURE to keep a private copy of the frontend for further development...) Nobody can open the .MDE in design mode. You can also look into securing the form using a "switchboard" to launch whatever you intend to show your users and hide the database window. Search this forum for the topic "Hide the Database Window" and you will see literally hundreds of references.
 
Maybe I am missing something here but I need help with splitting my database. This is not a shared database. I have my development db on a drive "H". Both the backend and frontend are in the same folder. I have split the db, password protected the backend, deleted the links on the frontend and relinked. I then used the Package Solution Wizard to package the application for distribution, specifying the install directory to be a sub-folder of the "My Documents" folder on the user's computer. However, the application comes up on the user's computer looking for the tables on the "H:" drive. Is there something I am doing wrong here?
 
Nobody can open the .MDE in design mode. You can also look into securing the form using a "switchboard" to launch
Doc -

Not quite accurate there. If you have a full version of Access you can open an MDE/ACCDE in design view. You just can't open forms, reports, macros or modules in design view. However, you CAN still open tables and queries in design view and even make changes, delete tables, queries, etc. while in an MDE file AND the changes will remain. So you really do need to use the DISABLE BYPASS KEY code to keep them out of the database window/Nav Pane, and uncheck the USE ACCESS SPECIAL KEYS to keep F11 from being used to display the database window or navigation pane.
 
Maybe I am missing something here but I need help with splitting my database. This is not a shared database. I have my development db on a drive "H". Both the backend and frontend are in the same folder. I have split the db, password protected the backend, deleted the links on the frontend and relinked. I then used the Package Solution Wizard to package the application for distribution, specifying the install directory to be a sub-folder of the "My Documents" folder on the user's computer. However, the application comes up on the user's computer looking for the tables on the "H:" drive. Is there something I am doing wrong here?

You will need to have code in the startup of your application to relink the tables.

See:

Boiler Plate Database

While it may have more things than you need at the momnet, it does have the relinking code you will need.
 
Last edited:

Users who are viewing this thread

Back
Top Bottom