lock sharepoint web app and keep data

[supmktg]

I have been developing access desktop apps for more than 15 years, but his is my first encounter with sharepoint web apps. I have spent months developing a hybrid app that uses the web app's sql azure db as the BE to a desktop app, with a couple of fairly complex web forms so remote users can place merchandise orders. The web app is now working exactly as I want it to, and I am now trying to lock the sharepoint web app so remote users can't edit it.

It seems that the only way to "lock" the web app is to save as/save for deployment. Unfortunately, save for deployment removes all of the data. This web app has about 30 supporting tables most of which are being used as the BE for the desktop app which is connected via ODBC. I would hope that there is a way to "lock" the app AND keep the data, but I just can't find it.

Can anyone help me?

Thanks,
Sup

 

[ldsouza]

Does giving the users read-only access to the SharePoint site not make the app un-editable?

 

[nyaworld]

I have been developing access desktop apps for more than 15 years, but his is my first encounter with sharepoint web apps. I have spent months developing a hybrid app that uses the web app's sql azure db as the BE to a desktop app, with a couple of fairly complex web forms so remote users can place merchandise orders. The web app is now working exactly as I want it to, and I am now trying to lock the sharepoint web app so remote users can't edit it.

It seems that the only way to "lock" the web app is to save as/save for deployment. Unfortunately, save for deployment removes all of the data. This web app has about 30 supporting tables most of which are being used as the BE for the desktop app which is connected via ODBC. I would hope that there is a way to "lock" the app AND keep the data, but I just can't find it.

Can anyone help me?

Thanks,
Sup

I have the same issue. Did you ever get this resolved?

 

[supmktg]

This took quite some time to ferret out, as the documentation from MS really doesn't exist.

The solution was to create a separate site that has its own permissions and then set the permissions for members to 'Contribute'. When creating the new site, make sure that it does not share the same permissions as the main site! That way, members can access the Web App (if you've shared it with them) but can't see the modify in Access icon.

This also required moving the entire Web App, along with the BE database to the new site. Which also required changing all of the connection settings for the desktop app to the new BE location.

HTH,
Sup