none
Unable to lock tables for deployment. RRS feed

  • Question

  • I need to make many iterative deployments, adding features, to an Access 2013 Web App. The information available leads you to believe this is possible, when you save the application "For Deployment". You are meant to be able lock static data tables and they will not be dropped. This does not work for me. The option to lock does appear in the dropdown menu list, but nothing happens when I click on it. It does not change to "Unlock" in the menu.

    Does this mean that I cannot use the "Deployment" approach for releases? Do I have to instead:

    1. "Save a Snapshot" to protect the data,

    2. delete the application from Office 365/SharePoint,

    3. upload the new version with data to Office 365/SharePoint,

    4. inform users of the new changed URL

    It really would be much better if this was transparent to the users.

    Thankyou for pointing me in the best direction here.

    Rohan

    Friday, October 2, 2015 3:07 PM

Answers

  • Hi Rohan,

    As far as I tested, the "Lock" feature works well for me. Here is the figure for your reference:

    Please ensure that you check the "Lock" option before you save the Access package like figure below:

    Hope it is helpful.

    Regards & Fei


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Wednesday, October 7, 2015 7:49 AM
    Moderator

All replies

  • Hi Rohan,

    If you want to lock the app so that users can't change it, we can deploy the Access web app via "Save for Deployment" instead of "Save as Snapshot". You can get more detail about this topic from link below:
    Create an Access app package

    Regards & Fei


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Monday, October 5, 2015 5:18 AM
    Moderator
  • That is my intended method. The benefit of any users not having the "Customize in Access" option available and I believe it is possible then to have iterative releases of app updates and not affecting the app's URL.

    It is unfortunate that this drops all tables data, especially as there are a number of static data or reference tables. It will be interesting to populate these tables as well as live data as well, what would be the best way? I have read that you can "Lock" tables making them not updateable and the rows are not dropped when "Save for Deployment" is performed. Perfect for reference tables.

    Unfortunately this does not work for me, when clicked nothing happens. I am lead to believe that the menu should show "Unlock" and a padlock icon appears next to the tables name on the access home view. Again nothing happens at all for me.

    Thanks for your help,

    Rohan

    Wednesday, October 7, 2015 12:26 AM
  • Hi Rohan,

    As far as I tested, the "Lock" feature works well for me. Here is the figure for your reference:

    Please ensure that you check the "Lock" option before you save the Access package like figure below:

    Hope it is helpful.

    Regards & Fei


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Wednesday, October 7, 2015 7:49 AM
    Moderator