Under System Summary, click the plus symbol next to Components. In the Run dialog box, type msinfo32 and then click OK. How do I use msinfo32 to check the file system?Ĭlick the Start button, and then click Run. If you have administrator privileges on the file server, you can run the msinfo32 command to determine the file system yourself. If you are not sure what file system your file server uses, ask the system administrator. Because users access the back-end database by using linked tables, it is less likely that intruders can obtain unauthorized access to the data by stealing the front-end database or by posing as an authorized user. Greater availability Because only the data is sent across the network, database transactions such as record edits are completed more quickly, which leaves the data more available to edit.Įnhanced security if you store the back-end database on a computer that uses the NTFS file system, you can use NTFS security features to help protect your data. In a shared database that is not split, the database objects themselves - tables, queries, forms, reports, macros and modules - are sent across the network, not just the data. Improved performance The performance of the database usually improves significantly because only the data is sent across the network. The benefits of a split database include the following: If you link to a table that is a SharePoint list, it creates a possibility for any malicious user to change the target of the link and potentially modify permissions on the SharePoint site as the connection information for linked tables is unencrypted. After you split the database, you must distribute the front-end database to your users.Ĭaution: To protect your data if your database has multiple end users, it is recommended that you do not share copies of a database that contains links to SharePoint lists.
To split a database, you use the Database Splitter Wizard. Each user interacts with the data by using a local copy of the front-end database.
When you split a database, you reorganize it into two files - a back-end database that contains the data tables, and a front-end database that contains all the other database objects such as queries, forms, and reports. If you split a web database, any web tables in that database will not be moved to the back-end database, and will not be reachable from the resulting front-end database.
For more information, see the online article Archive Access data. In some circumstances, you can archive data by splitting a database. You archive data by periodically moving older records to a different database, either because the database file grows too quickly to the file size limit, or because you want to keep the database file small and your data cleanly organized by time period.
This topic does not discuss how to archive data. So before you start fiddling around the edges for an easy solution (there isn't one) ask yourself who are you protecting the db from, what in particular and why.Splitting a database is not the same as archiving a database. You will also want to consider guarding against sql injection - a canny user can exploit this to destroy the database, copy all the tables, etc. You can disable things - but what can be disabled can be undisabled. You might also want to consider using SQL server as a back end which provides higher levels of data security.
(or tweaking a form to give them that ability - Note, password protecting the code does not prevent changes to the form or report so a user could change the recordsource by removing the criteria to see all records for example, a quick copy paste and your data is copied to another file). This involves not just preventing them having direct access to the tables but also not providing them with the ability to export everything to excel or to a printer. Also, compiled code is much less likely to become corrupted over time.ĭata is the most valuable (in my opinion) - so consider protecting against employees who might like to take a copy of the db or of certain data to one of your competitors. But it will protect against a 'who' user who likes to meddle. Compiling won't protect against a 'who' code competitor because they either have the resources or the budget to decompile. You can compile code - to decompile is difficult, but there are services out there which will do it for a price. You can hide things - which will deter some people but not others who know how to unhide things. The first things you should be asking yourself is who are you protecting the db from, what in particular and why. The question(s) you are asking has been asked many many times before and there are many possible solutions, although none guarantee complete security.