How to block exporting data from a geodatabase
You need to generate the licensed file gdb first and then that creates the protected file gdb as well as a License Definition File that is the input for generating the license file that would be installed on the computer that can access this licensed file gdb.
Another bit of information from my recent use of this tool is that is did not work from a network drive (ESRI was able to get the tool to work on their network). As a workaround, I copied the original file gdb to my c-drive and I was able to successfully run the 2 tools to generate the protected file gdb and it's associated license file.
That tool is looking for the license file, not the GDB.
Regards
For the geodatabase file it does not give the possibility
Your input was a Personal Geodatabase, not a File Geodatabase.
when I tried to generate license file geodatabase I have the following error
I recently used this licensing tool in an attempt to block the export of data from a file gdb, but I had issues labeling the data (complex labeling). This might not be an issue for you with simple labeling, so this is just an FYI.
BUG-000101771 [Layers in an existing MXD resourced to a licensed file geodatabase disappear from the map
That's them. Sorry to be terse - it's early in Redlands! The licensing tool has a parameter to set blocking of data export.
These tools grew out of software Esri built to license data products back when everything shipped on media.
I believe these are the ones bharold-esristaff is referring to. Though I didn't see an explicit comment in the instructions that it would block export, just that it would block display. Maybe there is more to this than what is currently in the Help?
Generate File Geodatabase License—Help | ArcGIS for Desktop
Generate Licensed File Geodatabase—Help | ArcGIS for Desktop
Chris Donohue, GISP
Standard and Advanced Desktop users can create a licensed file geodatabase and associated license file that blocks the export of vector data from Desktop applications. This should be backed up with an agreement. See the Data Management/File Geodatabase toolset.
And even through the Web you can still extract features.
If they have access to the data, what is to prevent them for just loading it in a new project... and nothing will stop them from accessing the data through a standalone python shell and exporting it external to the project. Attempt to minimize activity and use of data are easily circumvented and not worth the effort. If you don't want people to use it distribute what you want them to see or put it on the web, where you can control access
If the user can "see" the data, the export function is also available to him. See this post too: https://community.esri.com/thread/111899
My first reflection is to write a Python script to oblige the user to use a single folder for the export and on this folder it does not say the right of writing
Thank you very much for your reply,I want a user to work on my database without being able to copy or export the data.
And to add to FC's reply, if you don't want data to be used, you can simply distribute in a form that limits its capabilities or further use. For example you can shift, and rotate geometry ... you can anonymize attributes or remove all capabilities by delivering on the web
You really need to clarify your situation and purpose
So you want to prevent the user from exporting the data but at the same time still make the feature classes visible so that it can be viewed in ArcMap? I don't think that is possible.
Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
