Go Back   Access World Forums > Microsoft Access Discussion > General

 
Reply
 
Thread Tools Rate Thread Display Modes
Old 07-10-2019, 04:45 AM   #1
billgyrotech
Banned
 
Join Date: Apr 2013
Posts: 258
Thanks: 67
Thanked 3 Times in 3 Posts
billgyrotech is an unknown quantity at this point
Suggestions Before Splitting

Hello,


I plan to split this database and would appreciate any advice or suggestions before doing so. If there are any issues with codes or structure please let me know.


Thank you very much,
Bill


Last edited by billgyrotech; 08-05-2019 at 02:10 AM.
billgyrotech is offline   Reply With Quote
Old 07-12-2019, 10:42 AM   #2
billgyrotech
Banned
 
Join Date: Apr 2013
Posts: 258
Thanks: 67
Thanked 3 Times in 3 Posts
billgyrotech is an unknown quantity at this point
Re: Suggestions Before Splitting

Hello,


Maybe I didn't specify information correctly very sorry.


May I ask when I split the database how can I protect original files from being tampered with on my network?


Do I make a shortcut and password protect the file location?


I appreciate any advice,
Bill
billgyrotech is offline   Reply With Quote
Old 07-13-2019, 07:45 AM   #3
The_Doc_Man
Happy Retired Curmudgeon
 
Join Date: Feb 2001
Location: Suburban New Orleans, LA, USA
Posts: 14,708
Thanks: 93
Thanked 1,708 Times in 1,581 Posts
The_Doc_Man is a splendid one to behold The_Doc_Man is a splendid one to behold The_Doc_Man is a splendid one to behold The_Doc_Man is a splendid one to behold The_Doc_Man is a splendid one to behold The_Doc_Man is a splendid one to behold The_Doc_Man is a splendid one to behold
Re: Suggestions Before Splitting

Billy, here is the problem. If you are planning to distribute files on a network, this presumes that you are sending them to another computer. If you give a person the file to put on their computer somewhere, by implication the person will have not less than MODIFY permissions (if not FULL CONTROL). At that level, you cannot protect the files from having someone get into them. At most, you could password protect the files so as to encrypt them. However, unless you have taken suitable stops to block visibility of your DB's internal structure, they could just export everything to another blank DB and have tons of fun.

Search this forum for the topics of "Securing a database" and then see about implementing the protections described in those topics. In particular, if you see posts by isladogs, he has researched this topic heavily and has posted on it many times.

Now, the philosophy behind these suggestions: If someone wants to get into an Access database, they can. Notice I didn't qualify that? They can get in if they really want to. But you use the same theory for this as you do for hacker protection. A determined hacker can get it - but if you make it hard enough, they will look elsewhere for their fun. I.e., the trick is to make it not worth the extra effort.

Re-reading the second post, I realize there is a different interpretation. I have answered one of the possible interpretations. I'll address the other one.

If you worry about folks getting to your "original" files, don't distribute them. Set aside a public location on the net as the "repository" for the public copies of the files. Never put the private copies (master design copies) in harm's way. This is good for another reason. You should ALWAYS keep separate, private copies of any project in a private area, a totally different folder.

On the server we used for my biggest project, I had five folders: PROD, TEST, DEV, STAGING, and HISTORY. Users had access to PROD but only three people had access to the other folders. I would develop in DEV, test in TEST, and promote the new release through STAGING to the PROD folder. I would copy the old PROD copy of the DB to HISTORY before promoting the new copy from TEST. There would never be multiple copies or unsecured copies of the DB in PROD.

One thing I did at the last minute for each "promotion" was to never fully secure the DB until promotion time. When the tests were complete and the DB did what it needed to do, I copied that version to staging and finished the process of securing it. (Which included the stuff discussed in the FIRST part of this post.) Once I had the hardened version of the DB in staging, I did the archiving to the HISTORY folder and the promotion to the PROD folder, after which I cleaned up everything.

__________________
I'm a certified grandpa (3 times now) and proud of it.
Retired over one year and survived being home all day with the wife. She must really love me.
If I have helped you, please either click the thanks or click the scales.
The_Doc_Man is offline   Reply With Quote
The Following User Says Thank You to The_Doc_Man For This Useful Post:
billgyrotech (07-15-2019)
Old 07-15-2019, 02:33 AM   #4
billgyrotech
Banned
 
Join Date: Apr 2013
Posts: 258
Thanks: 67
Thanked 3 Times in 3 Posts
billgyrotech is an unknown quantity at this point
Re: Suggestions Before Splitting

Thanks very much Doc I will try follow your advice on having different stages like you have mentioned.


The database is close to deployment so hopefully I can have this done soon. I updated the new database with data from the old database 2 weeks ago so I will need to carry over the recent data. This hasn't been easy because there are some different fields and field names.


My process was to go through excel and make sure all of the tables had the same exact field names before importing.


Thanks again for your well thought out and detailed response to my post.


Cheers!

billgyrotech is offline   Reply With Quote
Reply

Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
New DB suggestions 2015imsjfw Tables 1 10-22-2017 03:38 PM
Suggestions please alexgore Tables 4 11-26-2012 04:41 AM
Need your suggestions jmriddic Queries 23 08-27-2012 12:04 PM
Suggestions! TimjHebert Tables 0 02-24-2005 07:20 AM
[SOLVED] Any suggestions? chris161 General 1 11-10-2002 01:29 PM




All times are GMT -8. The time now is 10:49 AM.


Microsoft Access Help
General
Tables
Queries
Forms
Reports
Macros
Modules & VBA
Theory & Practice
Access FAQs
Code Repository
Sample Databases
Video Tutorials

Featured Forum post


Sponsored Links


Powered by vBulletin®
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
(c) copyright 2017 Access World