How do these work? What are the differences? Pros and cons?
How do these work? What are the differences? Pros and cons?
accde files are executable files that you would distribute to the consumer of your app. Publishing your accdb file as an executable eliminates the ability to use the VBA editor by compiling all of your code so that it is only available during Run Time. You will not have access to class modules or general modules in an accde file. Nor will you have access to the navigation pane or the properties of objects.
Why didn't anyone tell me this. I was looking for something that could lock all those things like navigation pane to prevent the viewing of tables. I wanted to lock the table. But everyone tells me you can't do that. This may be the solution. So if I convert to ACCDE will I be to convert back if I need access to the navigation pane in the future?
No.
For my purposes, I just use accdb and employ code to lockdown the FE files, preventing access to toolbars, etc. Test the accde and see. I have been able to get to the table objects in previous versions of Access executable files.
You have to keep the non-executable version. Do edits in that file and then re-distribute the executable after each edit.
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.
So if I understand correctly, executable files (accde) are for viewing only. No edits can be made until you put the file back to non-executable format (accdb)?
Executable prevents modifying design and is intended for end user data entry/edit and report output.
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.
Ok so edits can be made just not design view edits.
Ummm.... Edits to the data can be made. Basically, your app needs to be able to function 100% in a run time environment.
However, if you are trying to restrict access to various things you will need to implement a combination of client settings and or VBA along with the executable. It does not sound like the executable alone will accomplish what you are after.
The executable will not include your VBA code. This is the big distinction. Like I said, try it out and see what it has to offer.